Release notes and known issues

OpenShift Dev Spaces runs on OpenShift 4.14–4.18 on the following CPU architectures:

For Red Hat OpenShift Dev Spaces 3.21, Red Hat will provide support for deployment, configuration, and use of the product.

There are some differences between Red Hat OpenShift Dev Spaces and the upstream project on which it is based, Eclipse Che:

Red Hat provides licensing and packaging to ensure enterprise-level support for OpenShift Dev Spaces.

Starting from this release, the admin can conceal particular editors on the User Dashboard using the dedicated environment variable CHE_HIDE_EDITORS_BY_ID in the Custom Resource :

spec:
  components:
    dashboard:
      deployment:
        containers:
        - env:
          - name: CHE_HIDE_EDITORS_BY_ID
            value: che-incubator/che-webstorm-server/latest, che-incubator/che-webstorm-server/next,
                   che-incubator/che-rubymine-server/latest, che-incubator/che-rubymine-server/next,
                   che-incubator/che-pycharm-server/latest, che-incubator/che-pycharm-server/next,
                   che-incubator/che-clion-server/latest, che-incubator/che-clion-server/next,
                   che-incubator/che-idea-server/latest, che-incubator/che-idea-server/next,
                   che-incubator/che-idea/latest, che-incubator/che-idea/next

Learn more about this feature in the official documentation.

Traefik version used by the operator has been updated to the v.3.3.5 version. More details about the new version are available in the official Traefik release notes.

Fabric8 Kubernetes Client used in the che-server component has been updated to the latest 7.1.0version. More details about the new version are available in the official Fabric8 Kubernetes Client release notes.

By default, the deprecated Projector-based IntelliJ IDEA Community edition is hidden on the User Dashboard from this release on, and will be completely removed in future releases. To enable the deprecated editor on the User Dashboard in the current version, use the dedicated environment variable CHE_SHOW_DEPRECATED_EDITORS in the Custom Resource:

spec:
  components:
    dashboard:
      deployment:
        containers:
        - env:
          - name: CHE_SHOW_DEPRECATED_EDITORS
            value: true

With this release, you can add an optional filter URL parameter on the Create Workspace page of the User Dashboard, and display only a portion of samples based on a particular technology e.g. Quarkus dashboard/#/create-workspace?filter=quarkus

Starting from this release, you can create a Cloud DeveloperEnvironment (CDE) by using a GitHub repository URL of a directory with a devfile, or a GitHub repository URL directly pointing to the devfile. Previously, you could only use URLs of the GitHub repository, branch, and tag, as well as raw devfile URLs to create a CDE.

Previously, there was a defect related to the connection to the Lightspeed service when you used the Ansible extension. Following error message would appear: "Error: invalid_request. Invalid redirect URI." This defect has been fixed in this release.

Previously, postStart commands were executed based on alphabetical order rather than the sequence in which they were listed in the devfile, leading to potential confusion, especially when a specific execution order is expected based on the listed sequence. Starting from this release, the execution happens in sequential order in the way the commands are listed in the postStart section of a devfile:

postStart:
  - command-one
  - command-two
  - command-three

Previously, setting disableWorkspaceCaBundleMount: true property in the Custom Resource (CR) did not stop mounting certificates into /etc/pki/ca-trust/extracted/pem/ directory. The defect has been fixed in this release.

Previously, when you deleted a workspace while using the per-user PVC strategy, the workspace might not have been deleted correctly if another workspace was running. In this release, a warning message will appear in such situations with a suggestion to stop running workspaces before you delete any.

Previously, when accepting Bitbucket server’s OAuth2 prompt, there was an unexpected error redirect page with the error stack trace: {"message":"Cannot invoke \"String.length()\" because \"this.input\" is null","trace"}. The defect has been fixed in this release.

The regression related to the controller.devfile.io/storage-type: ephemeral attribute has been fixed in this release, and Cloud Development Environments (CDEs) created from devfiles with this attribute now correctly use the emptyDir volumes.

Previously, there was a defect related to the loss of all Git history if a workspace pod was restarted with a default devfile when the persistent storage strategy specified in the CheCluster was per-workspace. The defect has been fixed in this release.

Before this release, it was not possible to use the desktop version of the JetBrains IntelliJ IDEA to connect to a workspace with a ubi9-based image over the JetBrains Gateway application. This defect has been fixed with this release.

There is a known issue affecting workspaces in Dev Spaces deployed to OpenShift Platform 4.18. When you start the workspace, the following error message appears: "Error creating DevWorkspace deployment: Container tools has state ImagePullBackOff".

There is a known issue with the desktop versions of JetBrains IDEs. Workspaces using these IDEs ignore idling timeouts specified by CheCluster properties such as secondsOfRunBeforeIdling, and secondsOfInactivityBeforeIdling. There is currently no workaround available.

There is currently a known issue affecting the use of the desktop versions of JetBrains IDEs with IBM Power, and IBM Z architectures. The downloaded JetBrains IDE binaries are not multi-arch, causing workspace startup to fail. There is currently no workaround available.

There is currently a known issue affecting workspaces running in the desktop version of JetBrains IntelliJ IDEA. If you close the IDE while the workspace is still running, you will receive the following error messages after re-opening the IDE: "There was an error in the connection provider", and "No connection handle was returned". There are multiple workarounds available.

There is currently a known issue affecting workspaces created by non-admin users and the JetBrains Gateway plugin. If you create workspaces in Dev Spaces as a non-admin user and use the same account to access Dev Spaces locally on your computer through the JetBrains Getaway plugin, the fetched list of workspaces will be empty. There is currently no workaround available.

There’s currently a known issue affecting workspaces using JetBrains Intellij IDEA in an air-gapped environment. If you choose JetBrains IntelliJ IDEA as your editor and try starting a workspace, the workspace startup will fail. A workaround is available.

There is a known issue when experimental refresh token mode is applied using the CHE_FORCE_REFRESH_PERSONAL_ACCESS_TOKEN property for the GitHub and Microsoft Azure DevOps OAuth providers. This causes the workspace starts to reload the dashboard cyclically, creating a new personal access token on each page restart. The refresh token mode works correctly for 'GitLab' and 'BitBucket' OAuth providers.