Menu Close

Chapter 2. Notable enhancements

2.1. Universal Developer Image consolidates all stack and plug-in sidecars into a single image

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.

Additional resources

2.2. Node.js version updated to 16

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.

Additional resources

2.3. Code samples implement the devfile v2 specification

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

Additional resources

2.4. Fuse Booster sample project updated to use the Red Hat build of OpenJDK 11 in the devfile

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

Additional resources

2.5. Support for Fuse devfiles on IBM Z and IBM Power

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.

Additional resources

2.6. Removal of the backup and recovery functionality

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.

Additional resources

2.7. Red Hat OpenShift Dev Spaces Operator enables the DevWorkspace engine by default

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

Additional resources

2.8. JetBrains IntelliJ IDEA editor now opens projects specified in the devfile

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.

Additional resources

2.9. Enabling admins to specify pod tolerations and node selector

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.

Additional resources

2.10. Improved startup performance of the Che-Theia IDE

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

Additional resources

2.11. OAuth 2.0 support for organizations' GitLab instances

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.

Additional resources

2.12. OpenJDK replaces JVM on IBM Power and IBM Z

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.

Additional resources

2.13. Parent devfile support

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

Additional resources

2.14. Version update of the Language Support for Apache Camel extension for Visual Studio Code

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.

Additional resources

2.15. Removal of support for some deployment environments

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:

  • OpenShift Container Platform 3.11
  • OpenShift Container Platform 4.8
  • OpenShift Container Platform 4.9
  • Red Hat OpenShift Dedicated 4.8
  • Red Hat OpenShift Dedicated 4.9
  • Red Hat OpenShift Service on AWS 4.8
  • Red Hat OpenShift Service on AWS 4.9

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:

  • OpenShift Container Platform 4.10
  • Red Hat OpenShift Dedicated 4.10
  • Red Hat OpenShift Service on AWS 4.10

Additional resources

2.16. Logs from the Che Gateway deployment

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.

Additional resources

2.17. Devfile no longer supports Visual Studio Code extensions

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.

Additional resources