Release Notes and Known Issues

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

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

CodeReady Workspaces 2.10 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.

When a VS Code extension have not used environment variables, the user had to set the configuration in the devfile scope. For an extension to modify the configuration of another extension, the user had to create a separate plug-in embedding both extensions. With this release, the user can set default static configurations in the plug-in’s meta.yaml.

Before this update, CodeReady Workspaces used the meta.yaml format.

With this update, CodeReady Workspaces is using: * Devfile v2 format to specify editors and plug-ins * an additional che-theia-plugin.yaml fragment to specify plug-ins preferences

This format enables to define: * dependencies between plug-ins * sidecar options * plug-in preferences

Editors in che-editors.yaml are defined using the devfile v2 specification, rather than the legacy meta.yaml syntax

The landing page is named Create Workspace rather than Get Started Page. The Quick Add tab includes an Import from Git section.

The per-user namespace strategy is the unique namespace strategy available in CodeReady Workspaces 2.10. Support for other namespace strategies is removed. The CodeReady Workspaces Operator does not allow upgrading installations using a namespace strategy other than per-user.

Latest python extension includes Jupyter support. This feature is available in CodeReady Workspaces.

All namespace strategies except the per-user strategy are unsupported.

This results in:

When all workspaces of a user are deleted, delete the PVC to free storage (common storage strategy).

Before this update, when a user didn’t have enough privileges to create a namespace, the workspace start failed. With this update, CodeReady Workspaces always uses the CodeReady Workspaces ServiceAccount to creates the user namespace. An administrator can configure CodeReady Workspaces to create the namespace using the user token.

Support for deploying CodeReady Workspaces on OpenShift Container Platform on IBM Power Systems is no longer a Technology Preview feature. CodeReady Workspaces 2.10 is fully supported on IBM Power Systems infrastructure.

The Resources Monitor Plug-in has enough permissions to read Pod information.

Propagate the specific reason the controller cannot reconcile Components and WorkspaceRoutings into the condition message.

Before this update, when the Dashboard failed to pre-load data, it didn’t show any error message. With this update, it displays an error message describing the reason of the failure.

Before this update, when running CodeReady Workspaces behind a proxy, cloning a git repository failed. With this update, when the editor is Che-Theia, cloning a git repository when running CodeReady Workspaces behind a proxy is possible.

Delve, a debugger for the Go programming language, is not available for IBM Z and IBM Power Systems architecture. Therefore, debugging features cannot be activated in the Go workspace in CodeReady Workspaces 2.10. An attempt to activate this feature results in the Failed to continue error message.

In a workspace created using the default Go devfile, some features fail because additional tools are missing. For instance, Auto-complete is unavailable.

The failure caused by a lack of OpenShift Container Platform cluster resources is accompanied by a misleading error message:

Your session has expired. Please, log in to CodeReady Workspaces again to get access to your OpenShift account.

This message will be fixed in the upcoming release.

If you start a task from My workspace multiple times, the task doesn’t end properly. The IDE displays a spinning-wheel icon as a replacement for the "✓" marker. As a consequence, the subsequent task execution can’t be started.

CodeReady Workspaces fails to run the PHP debug. PHP is a technology preview feature.

Get-Started devfiles have incorrect source location after the switch from multi-host to single-host exposure strategy.

When building the devfile registry, the build process updates the devfiles to set the source location of the artifact archives. When specifying multiple registries, the build process doesn’t update the archive source location in the devfiles properly.

The crwctl binaries don’t run on IBM Z and IBM Power Systems. These platforms are available uniquely as targets to deploy CodeReady Workspaces to.

CodeReady Workspaces is intermittently failing to create a workspace when the network is unstable. CodeReady Workspaces displays following error:

Failed to run the workspace: "Waiting for pod 'workspace9fbid1gnx7273d47.maven-545f8c9cf4-hw79f' was interrupted."

These 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 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.

The activation of the Appliance for Apache Camel K by Red Hat extension fails with the error message:

Activating extension `Appliance for Apache Camel K by Red Hat` failed: Dependent extension `redhat.vscode-commons` is not installed.

CodeReady Workspaces fails to start a workspace with a factory when the workspace is defined using the devfile 2.0 (DevWorkspace) specification. Then, CodeReady Workspaces displays the following error message:

Getting workspace detail data failed. Failed to fetch the workspace sprin-petclinic, reason: Could not retrieve the main URL for the running workspace.

The Python language server functionality does not work, and an error message is displayed while invoking the autocomplete and error highlighting functions.

The OpenShift Connector plug-in fails to deploy because of the inability to access the odo image in the disconnected environment.

Debug configurations are not loaded. The Debug panel displays:

No Configurations

After patching a CodeReady Workspaces 2.10 instances from multi-host to single-host, the "Create Workspace" Dashboard page displays incomplete UI with missing icons.

Bitbucket factory URL fails for public repositories outside OpenShift Container Platform for CodeReady Workspaces without Bitbucket OAuth enabled.