Release notes and known issues

OpenShift Dev Spaces runs on OpenShift 4.10–4.13 on the following CPU architectures:

For Red Hat OpenShift Dev Spaces 3.8, 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 update, admins can create a custom devfile registry from a clone of the devfile registry Git repository that is hosted on Bitbucket.

With this update, the User Preferences menu features a Personal Access Token tab. You can use the tab to manage GitHub, GitLab, Bitbucket, and Microsoft Azure DevOps personal access tokens. This applies to tokens created from the OpenShift Dev Spaces Dashboard UI as well as those created manually, using a Kubernetes secret.

This release features two CheCluster CRs fields for managing persistences related to workspaces $HOME directory:

Previously, trusted TLS certificates configured in OpenShift Dev Spaces were ignored if an OpenShift cluster-wide proxy was configured. With this update, you can configure DevWorkspace operator to avoid this undesired behavior.

With this update, commands defined in the parent devfile are now available in Microsoft Visual Studio Code - Open Source as tasks.

Previously, users had to provide a Git username when adding a personal access token. This step was redundant and caused errors. With this update, the step is removed from the procedure.

By default, OpenShift Dev Spaces hosts the IDE (Microsoft Visual Studio - Open Source Code or JetBrains IntelliJ IDEA Community Edition) in the first container specified in a devfile. With this update, you can specify the component that will host the IDE using the attribute controller.devfile.io/merge-contribution: true.

In the following example, the IDE will be hosted in "component2":

schemaVersion: 2.2.0
components:
  - name: component1
    container:
      image: quay.io/sclorg/postgresql-15-c9s:c9s
  - name: component2
     attributes:
       controller.devfile.io/merge-contribution: true
     container:
       image: quay.io/devfile/developer-base-image:latest

schemaVersion: 2.2.0
components:
  - name: component1
    container:
      image: quay.io/sclorg/postgresql-15-c9s:c9s
  - name: component2
     attributes:
       controller.devfile.io/merge-contribution: true
     container:
       image: quay.io/devfile/developer-base-image:latest

With this update, the TLS certificate of the OpenShift internal container registry is trusted by Podman. You can use Podman to pull images without adding the certificates manually.

With this update, the IDE of existing workspaces will be updated automatically after an upgrade or whenever the definition of the IDE changes.

With this update, the "Waiting for a workspace to start" step on the workspace loading page features 7 subtasks. This enhancement provides better progress feedback and makes troubleshooting easier.

With this update, the following metrics are available in the OpenShift Console Operator metrics:

Before this update, as a result of a bug, administrators were unable to enforce a list of containers to add to all workspaces. With this update, to automatically include specific containers in all workspaces in OpenShift Dev Spaces, administrators can specify a URI to a devfile defining a container component in devEnvironments.defaultPlugins of the CheCluster Custom Resource.

Before this update, starting a workspace from a branch of a Git repository with a slash (/) resulted in a "devfile could not be found" error. With this update, the issue is solved.

Before this fix, if an administrator customized some of the fields in the CheCluster Custom Resource (such as .spec.components.pluginRegistry.openVSXURL), the values could be overridden by the operator. With this update, the issue is fixed.

Before this update, developers could not add their Microsoft Azure DevOps Personal Access Token from the User Preferences menu in OpenShift Dev Spaces Dashboard. With this update, the issue is fixed.

Before this update, when a developer tried to authenticate with GitHub (for example to clone a repository or to use a GitHub extension) with an expired GitHub token or without a token, the operation could fail due to an authorization error. With this update, when no valid GitHub token is found, the user is informed how to generate it.

Before this update, when a developer started an empty workspace (not linked to a specific Git repository) or a OpenShift Dev Spaces sample, any consequent try to run git push would fail due to an authorization problem. This would occur even if the developer had pre-configured a personal access token for the Git service. With this update, pre-configured personal access tokens are mounted in empty workspaces and sample workspaces so that git push runs successfully.

There is a known issue where automatic installation of the recommended Microsoft Visual Studio Code - Open Source extensions fails if you’re using a Java or Ansible sample.

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.

There is currently a known issue for users who are using a Kubernetes Secret with their Git-provider credentials. The user name and email for Git operations in workspaces for those users are currently taken from the user-profile Secret of the <user>-devspaces namespace.

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