Release notes and known issues

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

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

OpenShift Dev Spaces 3.0 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, the following stacks and plug-ins are consolidated into a single Universal Developer Image (UDI) sidecar:

The UDI is now the only sidecar used in OpenShift Dev Spaces.

The UDI is available in OpenShift Dev Spaces, like the plug-ins and stack sidecars that the UDI has replaced: OpenShift Dev Spaces admins can use the image puller to pull the UDI. Users can specify the UDI in the devfile.

With this update, Node.js 16 is included in the Universal Developer Image sidecar that replaces the older stacks and plug-in sidecars.

Support for Node.js is aligned to the Node.js lifecycle.

Before this update, code samples implemented the devfile v1 specification. With this update, code samples are implementing the devfile v2 specification.

With this update, the Fuse Booster sample project uses the Red Hat build of OpenJDK 11 rather than 8.

With this update, Red Hat Fuse can be used in Red Hat OpenShift Dev Spaces on IBM Z and IBM Power.

The sample project and its associated devfile for Red Hat Fuse have been updated to work with Java 11 and can now be used on all supported architectures.

In OpenShift Dev Spaces 3.0, backing up and restoring a OpenShift Dev Spaces instance by using a backup server, such as SFTP or Amazon S3 or REST or the internal backup server, has been removed. The CheBackupServerConfiguration, CheClusterBackup, and CheClusterRestore custom resources are no longer used. Bug fixes and support are provided only through the end of the CodeReady Workspaces 2.15 lifecycle.

With this update, the Red Hat OpenShift Dev Spaces Operator enables the DevWorkspace engine by default from the new stable channel.

With this update, when you start a workspace using a devfile that specifies the JetBrains IntelliJ IDEA editor, the editor automatically opens the project(s) specified in the devfile.

With this update, OpenShift Dev Spaces admins can specify podTolerations and podNodeSelector for workspaces by setting a CustomCheProperty in the CheCluster custom resource. This is a global configuration and cannot be specified for a workspace or user.

With this update, the Che-Theia IDE loads in the workspace 20 seconds faster than previously.

With this update, OpenShift Dev Spaces supports private repositories on an organization’s own GitLab instance. OpenShift Dev Spaces admins can set up a GitLab-authorized application and configure OAuth 2.0 for a GitLab instance. No support is provided for private repositories on GitLab SaaS. This expands the OAuth 2.0 support that OpenShift Dev Spaces already provides for Bitbucket servers and GitHub.

Before this update, Eclipse OpenJ9 was the Java SE implementation for containers targeting IBM Power (ppc64le) and IBM Z (s390x) OpenShift clusters. With this update, the OpenJ9 JVM in the OpenShift containers for IBM Power (ppc64le) and IBM Z (s390x) is replaced by the Red Hat build of OpenJDK.

Installed CodeReady Workspaces instances, on update to Red Hat OpenShift Dev Spaces 3.0, switch over to use the new Universal Developer Image sidecar container that provides OpenJDK rather than OpenJ9 for Java 8 and 11.

Customers whose devfiles still reference the OpenJ9-based containers must edit their devfiles and replace plugin-java8-openj9-rhel8 and plugin-java11-openj9-rhel8 with udi-rhel8.

New samples in Red Hat OpenShift Dev Spaces 3.0 already use the new udi-rhel8 sidecar.

With this update, OpenShift Dev Spaces supports a devfile v2 that refers to a parent devfile.

Language Support for Apache Camel by Red Hat, the Visual Studio Code extension that adds Apache Camel language support for XML DSL and Java DSL code, is updated to version 0.1.5.

In Red Hat OpenShift Dev Spaces 3.0 (formerly CodeReady Workspaces), support for the following deployment environments is removed due to the switch to the DevWorkspace Operator:

Bug fixes and support are planned through the end of the 2.15 life cycle. During which, no new feature enhancements are made.

With Red Hat OpenShift Dev Spaces 3.0 (formerly CodeReady Workspaces), the supported deployment environments are the following:

With this update, the dsc server:logs command (formerly crwctl server:logs) can now retrieve logs from the Che Gateway deployment. This command can also retrieve logs from the Che Server, Operator, Dashboard, plug-in and devfile registries, and PostgreSQL deployments.

In OpenShift Dev Spaces 3.0, using the workspace devfile to specify Visual Studio Code extensions has been removed to meet the devfile v2 specification. Bug fixes and support are provided only through the end of the CodeReady Workspaces 2.15 lifecycle. To specify Visual Studio Code extensions, users must now use .vscode/extensions.json or .che/che-theia-plugins.yaml in their Git repositories. See https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.0/html/user_guide/adding-visual-studio-code-extension for more information.

With this update, as Technology Preview, OpenShift Dev Spaces 3.0.1 can be installed and tested on OpenShift Container Platform 4.11, OpenShift Dedicated 4.11, and Red Hat OpenShift Service on AWS (ROSA) 4.11, in addition to the supported OpenShift Container Platform 4.10, OpenShift Dedicated 4.10, and Red Hat OpenShift Service on AWS (ROSA) 4.10.

On IBM Z and IBM Power, the debugging features cannot be activated in the Go workspace in OpenShift Dev Spaces 3.0. Delve, the required debugger for the Go programming language, is not available for these platforms. An attempt to activate this feature results in the Failed to continue error message. This issue has no workaround.

Currently, Golang-based workspaces do not include basic language server features such as code autocompletion.

OpenShift Dev Spaces might fail to create a workspace when the network is unstable. OpenShift Dev Spaces displays an error such as Failed to run the workspace: "Waiting for pod 'workspace9fbid1gnx7273d47.maven-545f8c9cf4-hw79f' was interrupted." This issue has no workaround.

Currently, the following devfiles are not supported on IBM Z and IBM Power:

This issue has no workaround.

A workspace using Java with the JBoss EAP 7.3 devfile fails with the following error message: No delegateCommandHandler for vscode.java.startDebugSession. There is no workaround for this issue.

When a task is running and there is some networking issue, the terminal window is cleared and contains no text. Even when the connection is restored, the terminal remains empty and loading. There is no workaround for this issue.

The OpenShift Connector plug-in fails to deploy because of the inability to access the odo image in the disconnected environment. There is no workaround for this issue.

The DEBUG panel displays No Configurations in the drop-down list because no configurations are loaded.

On IBM Power, the list of supported image streams is missing, which causes component creation to fail. There is currently no workaround for this issue.

Upgrading a CodeReady Workspaces 2.15 instance with the DevWorkspace engine enabled (Technology Preview) is simpler than the upgrade procedure described in the Administration Guide.

When using the Cake-php sample, the Configure Apache Web Server DocumentRoots task fails with the following error: error sed: couldn’t open temporary file /etc/httpd/conf/sedSgv1Z4: Permission denied. There is currently no workaround for this issue.

Currently, the per-workspace workspace storage strategy is not supported due to the change to the DevWorkspace engine. With migration from CodeReady Workspaces 2.15 to OpenShift Dev Spaces 3.0, existing workspaces change to the common strategy. Setting the PVC storage size other than 10 GB is currently not possible. This issue has no workaround.

Currently, users might encounter a 403 Permission Denied error when logging in to OpenShift Dev Spaces.

Workaround: Log in to OpenShift Dev Spaces in a web browser using incognito mode.

See also #21352.

In workspaces that use the default Che-Theia IDE in a proxied environment, the Workspace panel might appear blank rather than showing available commands, terminals, and applications.

Currently, you might encounter a 503 Service Unavailable or 504 Gateway Time-out error message after refreshing the page of a stopped workspace.

Workaround: Restart the workspace from the dashboard.

In CodeReady Workspaces 2.15, users were able to edit their profile information in the Account page of the dashboard. Because OpenShift OAuth is now used exclusively for user management in OpenShift Dev Spaces 3.0, users can only edit their user profile within OpenShift. The Account page in the dashboard remains for display purposes only.

When launching a sample application from the workspace, users can encounter an error message such as 502 Bad Gateway or application not available. The cause of this error is the Theia IDE displaying the notification that the application is ready before the application startup is complete.

Workaround: Wait a minute or two, and reload the browser tab.

See the related issue #21377.

Currently on IBM Power, a workspace based on the Golang sample project might create files with file permissions that prevent workspace deletion.

Currently, using the OpenShift web console, OperatorHub, to create a new OpenShift Dev Spaces instance results in the instance deployed by default in the openshift-operators namespace for Operators.

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

Currently, the Welcome To Your Workspace page in Che-Theia workspaces might appear blank when the workspace loads. This is caused by a missing self-signed TLS certificate in the browser.

Currently, a workspace might fail to start if an applied ConfigMap includes environment variables, env.

Users running mvnw in disconnected or restricted environments might encounter a timeout error.

Currently, Maven commands might fail for JBoss EAP XP MicroProfile and JBoss EAP 7.4 because these devfiles use two separate users and containers.

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. This issue has no workaround.

Currently, using the Convert button in the OpenShift Dev Spaces dashboard to convert a Deprecated Node.js workspace with the node-debug or node-debug2 plug-in fails. The following error message is displayed:

Workspace conversion failed. Failed to create a new workspace from the devfile, reason: Unable to resolve theia plugins …​.

In OpenShift Dev Spaces 3.0, the node-debug and node-debug2 plug-ins have been updated to js-debug.

Currently, workspaces with Red Hat Fuse devfile v1 fail to start after conversion to devfile v2 by clicking the Convert button in the OpenShift Dev Spaces dashboard.

Currently, workspaces might fail to start in environments using a proxy. This failure happens if you attempted to customize proxy settings by configuring the DevWorkspaceOperatorConfig custom resource and a component was restarted after that. In that case, the workspace fails to start while the Progress tab shows Waiting for workspace to start.

Currently, when an OpenShift OAuth session expires, the dashboard page appears blank.

Currently, OpenShift Dev Spaces fails to start new workspaces with a clone of a GitHub-hosted repository when using the #https://github.com/<user_or_org>/<repository>/pull/<pull_request_id> URL syntax. The workspace-starting page displays the following error message: Failed to resolve a devfile. Failed to request factory resolver: Internal Server Error occurred.

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, starting a workspace that uses the Technology Preview Visual Studio Code on OpenShift with a self-signed TLS certificate results in a blank browser tab.

Currently, deploying the Vert.x Health Check Example application by running the 6-deploy-to-openshift command fails in disconnected environments. There is currently no workaround for this issue.

Currently, under certain conditions, such as OLM restart or cluster upgrade, the Dev Spaces Operator for OpenShift Dev Spaces 3.0.0 might automatically install the DevWorkspace Operator even if it is already present on the cluster. This might cause severe consequences: the OpenShift web terminal might stop working, or the DevWorkspace Operator admission webhooks might not work properly, which might affect the behavior of the cluster.

You can detect this issue on your cluster by checking Installed Operators in the OpenShift web console: if this problem is occurring, you see multiple entries for the DevWorkspace Operator or one entry that is stuck in a loop of Replacing and Pending.