Release Notes and Known Issues

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

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

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

An OpenShift CRD and Controller is handling workspace containers, rather than CodeReady Workspaces server. This transfer of responsibility enables a better orchestration. To manage the workspaces, OpenShift native tools and APIs are available, rather than a CodeReady Workspaces-server REST API using services of a custom CRD.

It enables:

The Image Puller can pre-download any CodeReady Workspaces image on all the nodes of an OpenShift cluster. The operator-metadata image doesn’t need pre-pulling and is not supported.

The Devfile allows for the definition of development environments in a repeatable and shareable manner. The specification continues to evolve as more tools, such as odo, adopt Devfiles and expand their usage. We are progressively introducing support in CodeReady Workspaces for the Devfile v2.x to allow for the following:

The VS Code YAML plug-in has been updated to version 0.14.0.

The VS Code Asciidoctor plug-in has been deprecated and will be removed in the future release.

Memory limits are handled at the plug-in and devfile levels. The globalMemory limits have been removed from the meta.yaml files inside the devfile registry.

The che-machine-exec and remote-runtime-injector plug-ins have defined resource limits.

The VS Code Language support for Camel K has been updated to version 0.0.24.

Users can pull images from private registries.

Some VS Code extensions must run in Multi-root mode. CodeReady Workspaces sets the Multi-root mode for all new workspaces.

To turn on the Multi-root mode in workspaces created in an earlier version, set the multiRoot parameter in the devfile:

attributes:
  multiRoot: 'on'

attributes:
  multiRoot: 'on'

All namespace strategies except the per-user strategy are deprecated and will be unsupported with a future release.

This change:

To access and authenticate a private GitLab repository using a factory URL pointer:

CodeReady Workspaces optionally collects Red Hat telemetry data from extensions that support it.

Upon starting a workspace whose devfile uses Git with SSH to clone a sample project, CodeReady Workspaces prompts you to provide an SSH key.

CodeReady Workspaces supports workspace creation using a GitLab-based factory URL.

The Bierner Markdown plug-in enables users to render Mermaid diagrams and flowchart graphs directly using Che-Theia Markdown preview.

The dashboard is running in a dedicated container rather than in the CodeReady Workspaces server container.

The Sonarlint plug-in is fully functional and works as expected.

CodeReady Workspaces 2.8 Node.js workspaces no longer fails to start after migration to the latest version.

All Java plug-ins (Java11, Java8, and Java) initialize as expected.

CodeReady Workspaces supports the ability to upload SSH keys that are password protected. When a workspace starts, the existing encrypted SSH keys are registered by the SSH agent.

The command Generate a new JWT authentication secret key of the PHP Laravel with MySQL getting started sample has been fixed. CodeReady Workspaces generates the JWT authentication secret key properly.

CodeReady Workspaces no longer fails to update when using external keycloak authentication.

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

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.

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.

These devfiles are not supported on IBM Z and IBM Power Systems:

Support for deploying CodeReady Workspaces on OpenShift Container Platform on IBM Power Systems and 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 VS Code Tooling for Apache Camel K by Red Hat plug-in fails with the message:

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

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