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.19, 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.

With this release, you can apply specific configuration properties to the Visual Studio Code - Open Source ("Code - OSS") editor using a dedicated ConfigMap:

apiVersion: v1
kind: ConfigMap
metadata:
  name: vscode-editor-configurations
data:
  extensions.json: |
    {
      "recommendations": [
          "dbaeumer.vscode-eslint",
          "github.vscode-pull-request-github"
      ]
    }
  settings.json: |
    {
      "window.header": "SOME HEADER MESSAGE",
      "window.commandCenter": false,
      "workbench.colorCustomizations": {
        "titleBar.activeBackground": "#CCA700",
        "titleBar.activeForeground": "#ffffff"
      }
    }
immutable: false

apiVersion: v1
kind: ConfigMap
metadata:
  name: vscode-editor-configurations
data:
  extensions.json: |
    {
      "recommendations": [
          "dbaeumer.vscode-eslint",
          "github.vscode-pull-request-github"
      ]
    }
  settings.json: |
    {
      "window.header": "SOME HEADER MESSAGE",
      "window.commandCenter": false,
      "workbench.colorCustomizations": {
        "titleBar.activeBackground": "#CCA700",
        "titleBar.activeForeground": "#ffffff"
      }
    }
immutable: false

Learn more about this feature in the official documentation.

The editor tiles displayed on the User Dashboard, including the license and version information, received a UI/UX enhancement.

With this release, you can view the full content of the .gitconfig file. Access it on the User Preferences Gitconfig tab by clicking Switch to Viewer.

Starting from this release, fuse-overlayfs will be detected automatically for the default Universal Developer Image.

With this release, the official documentation for configuring workspace endpoints base domain is available.

With this release, the official documentation for persisting the /home/user directory across workspace restarts is available.

The official documentation that explains how to configure proxy settings is available.

Starting from this release, the securityContext set in the CheCluster Custom Resource is applied to the Cloud Development Environment’s (CDE) che-gateway container.

With this release, if there is a proxy configured in the cluster, the proxy configuration is mounted to the che-dashboard container as environment variables: HTTP_PROXY, HTTPS_PROXY, and NO_PROXY.

With this release, you can use JetBrains Gateway to connect your local JetBrains IDE (IntelliJ IDEA Ultimate, PyCharm, WebStorm, RubyMine, and CLion) to a running Dev Spaces instance.

Starting from this release, there is a dedicated warning message for clusters that are behind a proxy, if you did not add the KUBERNETES_SERVICE_HOST environment variable to the no_proxylist environment variable.

Previously, a sporadic warning message could show up while Cloud Development Environment (CDE) was starting from a raw devfile. The defect has been fixed in this release.

Previously, the DevWorkspace 'storage-type' attribute was temporarily removed when restarting the Cloud Development Environment (CDE) from the local devfile. The defect has been fixed in this release.

Previously, revoking the GitHub token from the dashboard could fail with an "OAuth token for provider GitHub was not found" error message under certain conditions. The defect has been fixed in this release.

Previously, under certain conditions, a "TypeError: Cannot assign to read only property 0 of object `[objectArray]`" error message would appear when navigating to the User Preferences → Git Services tab. The defect has been fixed in this release.

Before this release, when you started a Cloud Development Environment (CDE) for a Bitbucket server private repository based on an SSH URL, the start was interrupted with an unexpected warning. The defect has been fixed in this release.

Previously, ServiceAccount token located at the path /var/run/secrets/kubernetes.io/serviceaccount/token was cached on the User Dashboard end and was not refreshed properly. The defect has been fixed in this release.

Regression related to the automatic restart from the local devfile for SSH URLs has been fixed in this release.

Kubeconfig format corruption after switching clusters and restarting the Cloud Development Environment (CDE) has been fixed in this release.

Previously, there was a "Cannot add property controller.devfile.io/bootstrap-devworkspace, object is not extensible" error when you tried to create a workspace with an SSH URL from the Dev Spaces dashboard. This defect has been fixed in this release.

Previously if devEnvironments.persistUserHome.enabled and devEnvironments.persistUserHome.disableInitContainer were both true, and if there was a file in the /home/user directory that would cause a stow conflict, the stow command would still run and fail due to the conflict. With this release, UBI and UDI entrypoint automatically add conflicting files into the /home/tooling/.stow-local-ignore to prevent the stow failure.

When creating new terminals in the Visual Studio Code - Open Source ("Code - OSS") editor with the New Terminal (Select a Container) option, the initial directory was not the current project directory (ex. /projects/<project-name>). This defect has been fixed in this release.

Before this release, there was an issue affecting Visual Studio Code - Open Source ("CODE - OSS") after you upgraded Dev Spaces from version 3.17.0 to 3.18.0. An outdated version of the IDE appeared when you opened a workspace previously created from a sample in Dev Spaces 3.17.0. This issue has been fixed in this release.

Before this release, there was an issue affecting the automatic setup of Git user.name and user.email in the `gitconfig file after you configured your access token (PAT) or OAuth. If you opened User Dashboard > Gitconfig page after PAT or OAuth configuration, you received the following error message: "Author identity unknown." The issue has been solved in 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’s currently a known issue with starting workspaces created with ubi9-based samples (ubi9-minimal, ubi-init, and ubi9) in the desktop version of JetBrains IntelliJ IDEA. The IDE does not load, causing the start of the workspace to fail after a period of time. Currently, there is 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.

Currently, the debugger in Microsoft Visual Studio Code - Open Source does not work in the .NET sample.