Release notes and known issues

OpenShift Dev Spaces 3.2 is available on the listed platforms with the listed supported installation methods:

For Red Hat OpenShift Dev Spaces 3.2, Red Hat will provide support for deployment, configuration, and use of the product.

OpenShift Dev Spaces 3.2 has been tested on Chrome version 101.0.4951.54 (Official Build) (64-bit).

The main differences between OpenShift Dev Spaces and Eclipse Che are:

Red Hat provides licensing, packaging, and support. Therefore, OpenShift Dev Spaces is considered a more stable product than the upstream Eclipse Che project.

With this update, Tech-Preview samples in the dashboard are listed after the fully suported ones.

With this update, OpenShift Dev Spaces supports the full functionality of CodeTogether, a pair-programming extension for Visual Studio Code. CodeTogether enables live sharing of Visual Studio Code sessions in OpenShift Dev Spaces workspaces.

With this update, you can use dsc server:delete --delete-all to uninstall the complete Red Hat OpenShift Dev Spaces instance, which includes its operator, related resources, and the OpenShift Dev Spaces namespace. The DevWorkspace Operator will be removed as well, if no other operator depends on it, such as the Web Terminal Operator.

With this update, a OpenShift Dev Spaces administrator can specify custom environment variables that will be applied to the containers of the core components of OpenShift Dev Spaces. You can specify those environment variables in the CheCluster Custom Resource.

With this update, OpenShift Dev Spaces administrators can define a default persistent storage strategy for new workspaces by using the CheCluster Custom Resource:

Users can override the storage strategy by entering a URL parameter when starting a new workspace. See URL parameter for the workspace storage.

The Dependency Analytics plug-in is upgraded to version 0.3.6.

This enhancement significantly improves workspace startup time.

With this update, administrators can configure OpenShift Dev Spaces to automatically connect to GitHub Enterprise Server, with subdomain isolation enabled, to retrieve and configure personal access tokens. This expands the OAuth 2.0 support that OpenShift Dev Spaces already provides for the GitHub Enterprise Cloud.

In OpenShift Dev Spaces 3.2, the Universal Developer Image (UDI) is updated as follows:

With this update, users can select an editor from the sample card in the dashboard. On the sample card, go to ⋮> Choose an editor and select one of the available editors.

Before this update, Git Large File Storage (LFS) was failing on the OpenShift Dev Spaces instances that used DevWorkspace Operator 0.15. It failed because the /etc/gitconfig file that contained the git-lfs configuration was automatically overwritten to set the name and email in Git commits in the workspace. With this update, upgrading DevWorkspace Operator to 0.16 resolves this issue.

Before this update, the dashboard might fail to automatically redirect to the IDE during workspace startup, which required manually reloading the browser tab. With this update, the dashboard automatically redirects to the IDE during workspace startup.

With this update, the OpenShift Lifecycle Manager treats the DevWorkspace Operator as a OpenShift Dev Spaces dependency, and the Red Hat OpenShift Dev Spaces Operator no longer deploys or manages the DevWorkspace Operator. This enhancement prevents occurrence of multiple deployments of the DevWorkspace Operator and avoids broken webhooks in an unsupported additional DevWorkspace Operator in the devworkspace-controller namespace.

Before this update, the rollback.sh script failed to roll back the migration from Dev Spaces to CodeReady Workspaces when rollback.sh was run directly after 1-prepare.sh. After this update, the rollback.sh script successfully rolls the migration back directly after 1-prepare.sh.

Before this update, the Bitbucket API client failed to resolve the server URI because of the path segments. With this update, the server URI is successfully resolved with the path segments.

Before this update, starting a new workspace by entering the URL of a Bitbucket.org-hosted public repository failed. With this update, you can successfully start a new workspace by entering the URL of a Bitbucket.org-hosted public repository that you want to be cloned into the workspace.

Before this update, the admin users were unable to deploy applications from a Dev Spaces workspace to OpenShift because those users' default projects were not defined. This problem affected all devfiles that projected an example command to deploy the application to OpenShift, including the Node.js devfiles. With this update, when you run the deploy command included with the sample devfile projects, the Dev Spaces workspace project is selected automatically, which resolves the issue.

With this update, Visual Studio Code is available as an alternative editor as Technology Preview for non-restricted environments.

In OpenShift Dev Spaces 3.4, the Eclipse Theia editor will be deprecated and its extensions will no longer be maintained. Eclipse Theia will be removed in a later release of OpenShift Dev Spaces. Red Hat will no longer provide bug fixes and support for Eclipse Theia in OpenShift Dev Spaces but will provide security fixes until its removal from OpenShift Dev Spaces. Although your users can continue to optionally use Eclipse Theia until its removal, you must prepare to migrate your users to Visual Studio Code - Open Source, which will be introduced as the new default editor in OpenShift Dev Spaces 3.3. Visual Studio Code - Open Source is already available as Technology Preview in OpenShift Dev Spaces 3.2 on non-air-gapped clusters and will receive air gap support in OpenShift Dev Spaces 3.3.

In OpenShift Dev Spaces 3.2, the following devfile samples have been removed:

Bug fixes and support are provided only through the end of the OpenShift Dev Spaces 3.1 lifecycle.

Currently, redeploying the DevWorkspace Operator fails after running the dsc server:delete --delete-all command.

Currently, there is a known issue with the in-browser Visual Studio Code editor in workspaces. This happens when you create more than one workspace with the same name. Visual Studio Code does not display pop-up notifications about recommended extensions and the dialog Do you trust the authors of the files in this folder?. Also, Visual Studio Code automatically reopens the last opened files from the previous workspace of the same name. There is currently no workaround for this issue.

Currently, starting a new workspace fails when entering the URL of a Git repository that does not contain a devfile and specifying the Technology Preview editor, Visual Studio Code. The error message states the following reason: Unable to resolve che-code plugins: Not able to find any dev container component in DevWorkspace. There is currently no workaround for this issue.

There is currently a known issue when starting workspaces that clone private Git repositories. After successfully cloning and reading the remote Git repository, the project-clone container fails to checkout a specified Git revision, for example a feature branch or PR branch. As a result of this error, the remote Git repository is cloned into a temporary directory named project-clone-<random_characters>.

Currently, pulling of a private container image fails when the image is pulled from a container registry that was added in the dashboard, User Preferences → Add Container Registry.

Currently, a workspace might fail to start, and then you might be unable to delete it. This is caused by a persistent volume claim (PVC) issue. Subsequently, the same problem occurs with other workspaces.

Currently, there is a known issue with the Java Gradle sample in restricted environments. Running the 1-build command to build an application might result in the FAILURE: Build failed with an exception error and failure to load a native library or not resolving a plug-in artifact in plug-in repositories. There is currently no workaround for this issue.

Currently, the name of the CheCluster custom resource remains the same as before upgrading from CodeReady Workspaces 2.15 to OpenShift Dev Spaces 3.2. Customers whose Checluster custom resource name is codeready-workspaces before the upgrade will find the same name after the upgrade. There is currently no workaround for this issue.

Currently, the Account page in the dashboard remains for display purposes only. To edit user profile, users must do so within OpenShift, because OpenShift OAuth is used for user management in OpenShift Dev Spaces.