Release notes and known issues

OpenShift Dev Spaces runs on OpenShift 4.12–4.16 on the following CPU architectures:

The following CPU architecture requires Openshift 4.13-4.16 to run OpenShift Dev Spaces:

For Red Hat OpenShift Dev Spaces 3.15, 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, podman login is performed automatically during workspace startup for all container registries configured in the User Preferences.

When you open a workspace from the User Dashboard, and a browser tab corresponding to the same workspace already exists, the switch to the browser tab happens automatically starting from this release. Previously a new browser tab was created whenever you tried opening a workspace from the User Dashboard.

Starting from this release, if the 'Restart Workspace from Local Devfile' command is failing due to an invalid devfile, the error notification message is more informative and contains the exact reason for the failure.

With this release, you can define annotations for all Cloud Development Environment (CDE) pods using a dedicated CustomResource field:

apiVersion: org.eclipse.che/v2
kind: CheCluster
spec:
  devEnvironments:
    workspacesPodAnnotations:
      cluster-autoscaler.kubernetes.io/safe-to-evict: false

apiVersion: org.eclipse.che/v2
kind: CheCluster
spec:
  devEnvironments:
    workspacesPodAnnotations:
      cluster-autoscaler.kubernetes.io/safe-to-evict: false

Previously, you could only configure custom editor definitions by modifying and rebuilding the Plugin Registry. Starting from this release, you can configure them by creating a dedicated ConfigMap.

Starting from this release, you can enable fuse-overlayfs for all CDEs.

Learn more about this feature in the official documentation.

With this release, the user experience during failures related to pre-configured Advanced Authorization is improved. When your access is denied, you will see a clear error message when accessing the User Dashboard.

Learn more about Advanced Authorization in the official documentation.

A new experimental feature that forces a refresh of the OAuth access token during workspace startup has been added in this release.

Learn more about this feature in the official documentation.

With this release, the new 2.3.0 schemaVersion of the devfile is supported for the CDE definition:

schemaVersion: 2.3.0
metadata:
  generateName: quarkus-api-example
attributes:
  controller.devfile.io/storage-type: ephemeral
components:
  - name: tools
    container:
      image: quay.io/devfile/universal-developer-image:ubi8-latest
      env:
        - name: QUARKUS_HTTP_HOST
          value: 0.0.0.0
...

schemaVersion: 2.3.0
metadata:
  generateName: quarkus-api-example
attributes:
  controller.devfile.io/storage-type: ephemeral
components:
  - name: tools
    container:
      image: quay.io/devfile/universal-developer-image:ubi8-latest
      env:
        - name: QUARKUS_HTTP_HOST
          value: 0.0.0.0
...

More details about version 2.3.0 are available in the official documentation.

Before this update, including a Bitbucket Personal Access Token (PAT) in workspaces on a OpenShift Dev Spaces installation with Bitbucket OAuth integration resulted in a "Backend is not available" error message. With this update, it’s possible to log in to the User Dashboard without issues.

From time to time, you could encounter multiple "401 Unauthorized" errors when opening a workspace with the Visual Studio Code - Open Source ("Code - OSS") editor. The defect has been fixed in this release.

Previously, after configuring container registries (quay.io, docker.io, etc.) from the User Dashboard and starting a workspace, you were not automatically logged into the configured registries. The defect has been fixed in this release.

Previously, strict validation prevented workspace creation from URLs such as user1@repository.example.com:/home/user1/repositories/myrepo.git. The defect has been fixed in this release.

In this release, the parsing error of the .code-workspace file that contains extra commas has been fixed:

{
	"folders": [
		{
			"name": "che-code",
			"path": "/projects/che-code",
		},
	]
}

{
	"folders": [
		{
			"name": "che-code",
			"path": "/projects/che-code",
		},
	]
}

An empty project used to be displayed in the project tree of the Visual Studio Code - Open Source ("Code - OSS") editor, if several starter projects were defined in the devfile. The defect has been fixed in this release.

Before this release, if GitHub OAuth configuration secrets were set up for both SaaS and Enterprise, and if the authorization agreement was accepted for only one of the providers, the authorization status was duplicated for both providers on the Git Services tab. The defect has been fixed in this release.

Before this release, you could encounter many processes labeled <defunct> in the workspace container while working in Visual Studio Code - Open Source ("Code - OSS").

Before this release,GOPATH and GOCACHE environment variables were not correctly set when running dedicated commands defined in a devfile. This resulted in failed tasks, for tasks such as the go build task. The defect has been fixed in this release.

Previously, mounting files using a ConfigMap, Secret, or PVC that conflict with stow directory files resulted in the stow command failure during the execution of the $HOME directory persistence. The defect has been fixed in this release.

There is a known issue affecting repositories without a devfile.yaml file. If you start a new workspace from a branch of such repository, the default branch (e.g. 'main') is used for project cloning instead of the expected branch.

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 '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.

There is a known issue with creating a workspace from GitHub Enterprise public repositories that have no personal access token (PAT) or OAuth configured. If you try to create a workspace from such a repository, you receive the following error message: "Failed to create the workspace. Cannot build factory with any of the provided parameters. Please check parameters correctness, and resend query."

There is a known issue with Ansible Lightspeed and connection to the Ansible server. If the OpenShift Dev Spaces environment is not under *.openshiftapps.com domain, Ansible Lightspeed can not connect to the Ansible server.

There is no workaround available.

There’s a known issue with FIPS compliance that results in certain cryptographic modules not being FIPS-validated. Below is a list of requirements and limitations for using FIPS with OpenShift Dev Spaces:

Once the cluster is up and running, install OpenShift Dev Spaces 3.7.1 (3.7-264) and verify that the latest DevWorkspace operator bundle 0.21.2 (0.21-7) or newer is also installed and updated. See https://catalog.redhat.com/software/containers/devworkspace/devworkspace-operator-bundle/60ec9f48744684587e2186a3

The resulting binaries can be scanned and should pass without error.

As they are not related to cryptography, they do not affect FIPS compliance.

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