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.7, 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, the included version of Traefik is updated from 2.8.1 to 2.9.6

With this update of the CheCluster Custom Resource, a gatewayContainer and projectCloneContainer sections are added under .spec.devEnvironments. This enhancement allows the administrators to specify the details of the container that will host the workspace reverse proxy (gateway) and the container that clones the remote Git repositories:

spec:
  devEnvironments:
    gatewayContainer:
        <container_settings>
    projectCloneContainer:
        <container_settings>

spec:
  devEnvironments:
    gatewayContainer:
        <container_settings>
    projectCloneContainer:
        <container_settings>

spec:
  devEnvironments:
    gatewayContainer:
      resources:
        limits:
          cpu: "0"

spec:
  devEnvironments:
    gatewayContainer:
      resources:
        limits:
          cpu: "0"

This enhancement introduces an Ansible sample in the OpenShift Dev Spaces dashboard for Ansible developers.

To use this sample in restricted environments, follow these steps:

This sample is currently supported for workspaces that run with the Microsoft Visual Studio Code - Open Source IDE. Support for workspaces that run with the JetBrains IntelliJ IDEA Community Edition IDE, which is a Technology Preview, will be added with a future release.

This sample is currently supported on AMD64 and Intel 64 (x86_64). Support for the IBM Power (ppc64le) and IBM Z (s390x) CPU architectures will be added with a future release.

Before this update, workspace URLs contained strings of random characters. With this update, the URLs contain the following parameters:

For example, if user john creates a quarkus-todo workspace that exposes a backend endpoint using my-dev-spaces-instance.com, the resulting URLs are as follows:

With this update, developers can use the .code-workspace file to configure the workspaces in Microsoft Visual Studio Code - Open Source. Specify the .code-workspaces file for your project in the devfile with the environment variable VSCODE_DEFAULT_WORKSPACE:

schemaVersion: 2.2.0
(...)
components:
- name: dev-tools
  container:
    (...)
    env:
    - name: VSCODE_DEFAULT_WORKSPACE
      value: "/projects/che-demo-app/che-demo.code-workspace"

schemaVersion: 2.2.0
(...)
components:
- name: dev-tools
  container:
    (...)
    env:
    - name: VSCODE_DEFAULT_WORKSPACE
      value: "/projects/che-demo-app/che-demo.code-workspace"

With this update, the trusted enterprise Certificate Authorities (CAs) specified for workspaces, are used by Microsoft Visual Studio Code - Open Source to trust any TLS certificate signed by the specified CAs. Microsoft Visual Studio Code - Open Source can access Open VSX registry instances that use them.

With this update, Microsoft Visual Studio - Open Source honors the NO_PROXY environment variable. You can use the environment variable to specify hosts that should be connected directly and not through a corporate proxy.

This enhancement introduces an Ansible sample in the OpenShift Dev Spaces dashboard for Ansible developers.

To use this sample in restricted environments, follow these steps:

This sample is currently supported for workspaces that run with the Microsoft Visual Studio Code - Open Source IDE. Support for workspaces that run with the JetBrains IntelliJ IDEA Community Edition IDE, which is a Technology Preview, will be added with a future release.

This sample is currently supported on AMD64 and Intel 64 (x86_64). Support for the IBM Power (ppc64le) and IBM Z (s390x) CPU architectures will be added with a future release.

Before this update, webviews in Microsoft Visual Studio Code - Open Source did not render correctly in restricted environments. This issue occurred because the browser could not download static resources from the public Internet behind a proxy. With this update, the OpenShift Dev Spaces build of Microsoft Visual Studio Code - Open Source serves those resources directly from its server, which is usually accessible through proxies.

Before this update, as a result of a bug, Bitbucket Server access tokens were not detected as Kubernetes Secrets. The editor in the workspace did not detect an access token for Bitbucket Server. With this update, individual users can resume using Bitbucket Server access tokens as Kubernetes Secrets.

Before this update, new workspaces using a raw link to a devfile hosted by GitLab or Bitbucket could fail to start with the following error message: "Internal Server Error occurred". With this update, the issue is solved.

Before this update, workspaces failed to start when a Kubernetes component in the devfile used the uri field and regardless of the value of deployByDefault. As a result, some of the samples in the Developer view of the OpenShift web console failed to load in OpenShift Dev Spaces. With this update, Kubernetes components that have the deployByDefault field set to false are ignored in devfiles when a workspace starts.

Before this update, for Git repositories that are hosted by Microsoft Azure DevOps, new workspaces might fail to start due to a Workspace does not exist error. With this update, the issue is resolved.

Before this update, developers could experience a delay between typing and the characters appearing in the Microsoft Visual Studio Code - Open Source embedded terminal. With this update, the default GPU acceleration is changed to canvas which solves the issue.

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.