Chapter 2. Notable enhancements

With this update, the CheCluster custom resource definition is improved to reflect the changes introduced with the switch to the DevWorkspace Operator. OpenShift Dev Spaces administrators now get a shorter and simpler configuration file to maintain.

With this update, OpenShift Dev Spaces administrators can now set the default in-workspace editor and default container. The default editor is used when the editor is not specified by using the .che/che-editor.yaml file in the Git repository or by using the che-editor URL parameter. The default container is used when a developer doesn’t specify a devfile when starting a new workspace. OpenShift Dev Spaces administrators can set these defaults by using the new defaultEditor and defaultComponent fields in the workspaces section of the CheCluster custom resource.

Before this update, the browser tab of a stopped workspace displayed a 503 error page when you visited the URL of the workspace or refreshed the tab. With this update, rather than seeing the 503 error, you see a warning message, a link to restart the workspace, and a link to return to the dashboard.

In OpenShift Dev Spaces 3.1, the IntelliJ IDEA Community sample has been removed from the dashboard because you can use this editor with all of the samples. To start a workspace with this editor, use the factory URL parameter or create a .che/che-editor.yaml file in the Git repository. See the User Guide section Selecting a workspace IDE.

This update expands the supported platforms for OpenShift Dev Spaces 3.1 to include OpenShift Container Platform 4.11, OpenShift Dedicated 4.11, and Red Hat OpenShift Service on AWS (ROSA) 4.11, in addition to the already supported OpenShift Container Platform 4.10, OpenShift Dedicated 4.10, and Red Hat OpenShift Service on AWS (ROSA) 4.10.