Chapter 2. New features and enhancements

With this release, you can specify a passphrase while adding a new SSH key using the "SSH Keys" tab in the User Preferences.

This feature is a Technology Preview feature, and disabled by default. In order to use this feature, config.enableExperimentalFeatures: true must be set in the DevWorkspaceOperatorConfig Custom Resource.

With this release, you can restrict the total number of the 'Running' workspaces on a cluster using the maxNumberOfRunningWorkspacesPerCluster CheCluster CR property.

Learn more about this feature in the official documentation.

With this release, you can specify the list of URLs based on which Cloud Development Environments (CDEs) can be initialized using the dedicated optional allowedSources CheCluster CR property:

     "devEnvironments": {
       "allowedSources": {
         "urls": ["url_1", "url_2"]
       }

Learn more about this feature in the official documentation.

With this release, you can deploy operands managed by the operator (dashboard, gateway, plugin-registry etc.) on the specific cluster nodes using the dedicated nodeSelector and tolerations properties CR properties:

  dashboard:
      deployment:
        nodeSelector:
        tolerations:

With this release, you can conceal editor definitions. This is useful when an admin wants to hide particular editor(s) from the Dashboard UI, e.g. remove the IntelliJ and have only Visual Studio Code - Open Source visible.

Learn more about the procedure in the official documentation.

With this release, you can provide endpoint annotations in the devfile. For example, the following devfile snippet will create an ingress or route with the annotation foo: bar on Cloud Development Environment (CDE) startup:

components:
  - container:
      endpoints:
        - name: my-endpoint
          annotation:
            foo: bar
            ...

The spec.devEnvironments.runtimeClassName property has been added to the CheCluster CR. This property sets the spec.runtimeClassName for all Cloud Development Environment (CDE) pods. The controller.devfile.io/runtime-class attribute for the CDE has precedence over the CheCluster spec.devEnvironments.runtimeClassName property.

With the release, the FailedScheduling event is the default value for the spec.devEnvironments.ignoredUnrecoverableEvents property. This is beneficial when the cluster has an autoscaler configured. If a Cloud Development Environment (CDE) pod cannot be scheduled on any node causing a FailedScheduling event, the CDE startup will be retried when the new node is provisioned.