Release Notes and Known Issues

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

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

CodeReady Workspaces 2.13 has been tested on Chrome version 94.0.4606.81 (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, CodeReady Workspaces contained JavaEE dependencies. With this update, CodeReady Workspaces contains JakartaEE dependencies.

With this update, on a CodeReady Workspaces instance with Dev Workspace engine, users can specify their choices of an editor with the che-editor factory link parameter. For example, https://codeready-<openshift_deployment_name>.<domain_name>#<repository-url>?che-editor=eclipse/che&#45;theia/latest is to select Che-Theia.

This enhancement standardizes and simplifies configuration of Git hosting services (GitLab, GitHub, and Bitbucket) for CodeReady Workspaces workspaces, with OpenShift secrets and OAuth.

New CodeReady Workspaces deployments use PostgreSQL 13. Before this update, CodeReady Workspaces deployments were using PostgreSQL 9.6. PostgreSQL 9.6 is deprecated. Migrate deployments created by an earlier version of CodeReady Workspaces. See: Migrating from PostgreSQL 9 to PostgreSQL 13.

With this update, when using the Dev Workspace engine, you can specify the devfile path when creating a workspace from a URL. Use the devfilePath parameter. It enables the coexistence of two devfiles in the same repository, to support the version 1 to version 2 migration.

Before this update, when using the Dev Workspace engine, CodeReady Workspaces workspaces were missing required configuration settings, such as proxy or self-signed certificates. With this update, the settings stored by the CodeReady Workspaces server are propagated to the workspaces.

With this update, CodeReady Workspaces supports creating workspaces from a devfile version 2 on all workspace engines. Before this update, using the Dev Workspace engine was required.

With this update, CodeReady Workspaces workspaces support the Git Large File Storage (LFS) extension.

The OpenShift Connector extension for Visual Studio Code has been upgraded to version 0.2.11.

Before this update, the CodeReady Workspaces operator crashed with an Out Of Memory (OOM) error in OpenShift clusters with multiple projects. With this update, the memory limit is sufficient.

CodeReady Workspaces includes a version of OpenShift Connector that doesn’t support OpenShift Container Platform 3.11.

To use the OpenShift Connector inside CodeReady Workspaces, consider one of the following options:

OpenShift Container Platform 3.11 will become deprecated in June 2022, and will no longer be supported by CodeReady Workspaces after that date.

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

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.13 instance from multi-host to single-host, the Dashboard Create Workspace page displays an incomplete UI with missing icons.

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

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:

Support for deploying CodeReady Workspaces 2.13 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 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.

After deploying the CodeReady Workspaces Operator form the tech-preview Operator channel in the default namespace and creating a CheCluster Custom Resource in the default namespace, the OpenShift Prometheus UI doesn’t display the metrics.

Upgrading an instance with the Dev Workspace engine enabled requires manual steps.

Support for deploying CodeReady Workspaces 2.13 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 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 using OperatorHub to install CodeReady Workspaces with the Dev Workspace engine, the Image Puller can’t be enabled. The Image Puller doesn’t work with the tech-preview-latest-all-namespaces channel

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

The Quarkus sample workspace from tech-preview channel fails to clone Git repositories in a restricted environment.

The welcome page tab titled "Red Hat CodeReady Workspaces" may at times load with no content.