This section describes the availability and the supported installation methods of CodeReady Workspaces 2.11 on OpenShift Container Platform 4.6, 3.11, and OpenShift Dedicated.

For Red Hat CodeReady Workspaces 2.11, Red Hat will provide support for deployment, configuration, and use of the product.

CodeReady Workspaces 2.11 has been tested on Chrome version 90.0.4430.72 (Official Build) (64-bit).

The main differences between CodeReady Workspaces and Eclipse Che are:

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

Before this update, the Che-Theia editor displayed an empty file explorer when the workspace contained no projects. For the user, it was not obvious how to create a file or clone a repository. With this update, the Che-Theia editor displays the Open Folder and Clone Repository buttons in the file explorer.

With this update, the GitHub factory implementation supports reading from a private repository. Users can load a devfile hosted in a private repository. The added support for OpenShift OAuth token authentication allows working with repositories behind an RH-SSO organization.

Before this release, using the Image Puller involved providing a list of images to pre-pull. With this release, when installed with CodeReady Workspaces using OperatorHub, the Image Puller auto-pulls the relevant images. The images to pre-pull are the default images used for workspace startup, including Theia, plugin broker, and sidecar images.

The Tool-set for the Apache Camel K extension has been upgraded to version 0.0.26.

With this update, the Image Puller can pre-pull any CodeReady Workspaces image on all the Nodes of an OpenShift cluster. This includes scratch images.

Before this update, CodeReady Workspaces could not create a workspace using a factory link to an on-premises GitLab repository without a branch named master. With this update, the GitLab file reading behavior omits the master branch name by default, and CodeReady Workspaces can create a factory link to a GitLab repository that has the default branch other than master.

On IBM Z and IBM Power Systems, the debugging features cannot be activated in the Go workspace in CodeReady Workspaces 2.11. 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.

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

A lack of OpenShift Container Platform cluster resources causes a failure. This failure causes a misleading message: Your session has expired. Please, log in to CodeReady Workspaces again to get access to your OpenShift account.

Currently, when you start a task from My workspace multiple times, the task does not end. The IDE displays the loading circle but no check mark (✓). As a result, the IDE cannot start the following task.

Currently, CodeReady Workspaces fails to run a PHP debug session with the following error message: There was an error starting the debug session, check the logs for more details. PHP is a Technology Preview feature. There is currently no workaround for this issue.

When using the single-host strategy for workspace exposure, attempting to clone a workspace from a Quick Add sample results in an error. There is currently no workaround for this issue.

The crwctl binaries do not run on IBM Z and IBM Power Systems. These platforms are available as targets for deploying CodeReady Workspaces.

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

The following devfiles are not supported on IBM Z and IBM Power Systems:

Support for deploying CodeReady Workspaces on OpenShift Container Platform on IBM Z is available as a Technology Preview feature. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not fully function. Red Hat does not suggest using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

When starting a workspace, users might receive the following error message: Your session has expired. Please login to Che again to get access to your OpenShift account.

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.

After patching the CodeReady Workspaces 2.11 instance from multi-host to single-host, the Dashboard Create Workspace page displays an incomplete UI with missing icons.

Currently, the Python workspace displays unexpected dialog boxes, including the following error: Python is not installed. Please download and install Python before using the extension. There is currently no workaround for this issue.

The Java analytic plugin doesn’t work with the jboss-eap-quickstart sample project, used by the JBoss EAP XP 3.0 MicroProfile devfile.

Currently, after upgrading DevWorkspace 2.10.1 to 2.11, CodeReady Workspaces fails to create a workspace with the following error: Getting workspace detail data failed. Failed to fetch the workspace <workspace_name>, reason: Could not get exposed endpoints for DevWorkspace: controller not ready to resolve the workspace routing.

Don’t deploy CodeReady Workspaces to the openshift-workspaces namespace on OpenShift Dedicated and ROSA.

Support for deploying CodeReady Workspaces 2.11 with the Dev Workspace engine is available as a Technology Preview feature, for OpenShift Container Platform 4.8. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not suggest using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

Upstream sample devfiles are designed for Eclipse Che. CodeReady Workspaces doesn’t support these samples. A workspace running with the Dev Workspace engine might fail to start when using an upstream sample devfile.

On IBM Power Systems, the list of supported image streams is missing, which causes component creation to fail.

When the Kubernetes Image Puller is installed, uninstalling CodeReady Workspaces fails, meaning: