Release notes and known issues

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

For Red Hat OpenShift Dev Spaces 3.11, 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, the following properties for advanced authorization are available in the Custom Resource.

allowUsers, allowGroups, denyUsers, denyGroups

This configuration allows the cluster administrator to explicitly manage the onboarding and curate the access for Red Hat OpenShift Dev Spaces.

With this release, OAuth2 authorization code flow using callbacks and URI handlers is supported. You can now use Microsoft Visual Studio Code - Open Source extensions that use this flow, for example the Ansible extension with the AI-powered Lightspeed service.

With this release, you can use the Git Services tab in the User Preferences dashboard page to reject the authorization opt-out flag.

With this release, you can configure personal access tokens for GitHub Enterprise Server in the User Dashboard.

With this release, following page features are available for workspaces that failed at startup:

With this release, private raw URLs with the ?token parameter on github.com are supported.

With this release, Java 17 is used by default in the UDI.

With this release, you can configure SSH keys and open workspaces using all Git providers. This includes GitHub, Gitlab, Bitbucket, and Microsoft Azure, as well as Git providers that were previously not supported:

With this release, you can add SSH keys on the User Dashboard by copying and pasting them.

With this release, devfiles with schemaVersion 2.2.1 and 2.2.2 are supported.

Before this update, the HOSTNAME environment variable could be overridden. This resulted in the Microsoft Visual Studio Code - Open Source extension che-resource-monitor not working properly. With this update, the HOSTNAME environment variable is copied to the DEVWORKSPACE_POD_NAME environment variable before the IDE is launched to create a backup source of the relevant data.

Before this update, workspaces from public GitHub Enterprise Server repositories failed to start if no OAuth or Personal Access Token (PAT) was configured. With this update, the issue is fixed.

Before this update, accessing OpenShift API from a workspace in a disconnected cluster failed with the following error message: "HttpError: HTTP request failed". With this update, the issue is fixed.

Before this update, the GitHub Device Authentication was not available in the command palette. This resulted in the following GitHub Copilot error: "Copilot could not connect to server. Extension activation failed: "Request failed with status code 401". With this update, the issue is fixed.

Before this update, the Microsoft Visual Studio Code - Open Source launcher was adding projects from devfile.yaml to .vscode-workspace configuration file only during the initial workspace startup. If you added a new project (or dependent project) to the devfile and restarted the workspace using the "Restart Workspace from Local Devfile" option, the new project was not added to the configuration file. This resulted in you not seeing the project even though all the projects were cloned in the /projects folder. With this release, projects are correctly updated in the .vscode-workspace configuration file.

Before this update, BitBucket OAuth 1.0 was not displayed in the Git Services tab. With this update, the issue is fixed.

Before this update, defaultPlugins defined in the Custom Resource were not applied during workspace startup. With this update, the issue is fixed. You can also add additional sidecar plugins using a devfile.yaml reference:

     devEnvironments:
       - editor: che-incubator/che-code/insiders
         plugins:
            - >-
              https://example.com/devfile.yaml

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 is a known issue affecting Ansible Lightspeed and the embedded plugin registry. After logging into Ansible Lightspeed using the embedded plugin registry, you are not redirected to OpenShift Dev Spaces.

There is a known issue affecting projects created in/cloned into an empty workspace. The default folder for the projects is the "/home/user" directory. However, the changes to the folder are not saved after you restart the workspace.

There is a known issue with automatic installation of the recommended Microsoft Visual Studio Code - Open Source extensions. After you install the extensions using the embedded plugin registry, the extensions are stuck in "Installing" status in the Extensions menu.

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 where recommended extensions are not installed automatically in Microsoft Visual Studio Code - Open Source.

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