Release notes and known issues

OpenShift Dev Spaces runs on OpenShift 4.15–4.20 on the following CPU architectures:

For Red Hat OpenShift Dev Spaces 3.25, 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.

You can now connect to multiple Dev Spaces workspaces simultaneously by using the JetBrains Gateway plugin. Previously, the plugin restricted you to a single active connection. This limitation is now removed.

Dev Spaces now supports running nested containers, which allows you to use commands like podman run directly in a workspace without kubedock. To enable this feature, set spec.devEnvironments.disableContainerRunCapabilities to false in the CheCluster custom resource.

Known issue

On OpenShift Container Platform 4.20.3, an SELinux regression prevents nested containers from functioning on clusters that were upgraded from version 4.17. This issue is specific to long-running, upgraded clusters and does not affect new clusters installed with OpenShift Container Platform 4.19 or 4.20.

For more information, see the documentation and the OpenShift Container Platform 4.20 release notes.

You can now specify a name for a workspace when you create it from the Getting Started page on the User Dashboard.

You can now rename an existing workspace by adding the kubernetes.io/metadata.name label to the DevWorkspace custom resource.

This release changes the default behavior for Persistent Volume Claims (PVCs) that are synchronized to user namespaces. Previously, deleting the source PVC would also delete the synchronized PVCs in each user namespace.

To prevent accidental data loss, synchronized PVCs are no longer deleted by default when the source PVC is removed. This behavior applies to PVCs configured by following the procedure in the Configuring a user namespace documentation.

Previously, when you attempted to add a personal access token (PAT) for a Bitbucket Server from the User Preferences > Personal Access Tokens page, no clear error was shown if the server’s TLS certificate was not imported into Dev Spaces.

Now, if the certificate is missing or untrusted, the User Dashboard displays the following error message: The required SSL certificate is missing or not trusted by the system. Please contact your administrator.

The che-code editor, which is based on Visual Studio Code - Open Source (Code - OSS), is now updated to version 1.103.2.

You can read about the new features and fixes from the upstream project in the VS Code release notes.

If the CheCluster controller fails to reconcile, the devspaces-operator pod now provides more detailed error logs to aid in troubleshooting.

You can now connect to a DevWorkspace by using the SSH protocol from your local VS Code-based editor.

Workspaces using JetBrains IDEs now correctly respect the idling timeouts specified by the CheCluster properties secondsOfRunBeforeIdling and secondsOfInactivityBeforeIdling.

Previously, these workspaces ignored timeout settings. With this update, user activity is accurately tracked by the editor’s cursor position to determine when a workspace is idled and should be stopped.

Previously, on the Dashboard, enabling the Create New switch (in the Select a Sample section) would incorrectly add the policies.create=perclick parameter to the Git repo URL field. This behavior was confusing and not documented.

This issue is now resolved. The Create New switch no-all-caps no longer affects the Git repo URL field. To force the creation of a new workspace from a Git URL, you must use the documented ?new parameter in the URL.

For more information, see the documentation about Starting a workspace from a Git repository URL.

This release fixes a bug in the Add/Edit Personal Access Token (PAT) window and adds Bitbucket to the list of supported providers[cite: 5210]. [cite_start]When you edit a Bitbucket SaaS OAuth 2 token, Bitbucket is now automatically selected in the Provider Name dropdown menu.

This release fixes a bug where the private_token URL parameter in the Git repo URL field on the Create Workspace page was ignored. Now, if you include private_token in the repo URL, the workspace correctly uses it to authenticate.

Previously, changes in .che/che-editor.yaml were not applied when a workspace was restarted. This release fixes that bug, ensuring that custom editor updates defined in .che/che-editor.yaml are correctly applied after restarting the workspace.

To reduce the number of login steps, the JetBrains Gateway landing page now displays a link to the cluster token request page after the DevWorkspace starts.

The Red Hat OpenShift Dev Spaces Operator does not currently support OpenShift clusters configured with Bring Your Own (BYO) External Authentication.

Dev Spaces currently relies on the built-in OpenShift OAuth server. Configurations that replace the built-in OAuth server with external corporate OIDC Identity Providers (IdPs) are not supported in this release.

There is a known issue with the desktop version of Visual Studio Code editor. Workspaces using these editor ignore idling timeouts specified by CheCluster properties such as secondsOfRunBeforeIdling and secondsOfInactivityBeforeIdling. There is currently no workaround available.

There is a known issue affecting the use of IntelliJ IDEA Ultimate IDE on the arm64 architecture. When you start a workspace in the IDE, the following error message appears: "504 Gateway Time-out". There is no workaround available.

There is a known issue with using the Ansible sample on the `arm64`architecture. The Ansible sample fails to start and the following error message appears: "Error creating DevWorkspace deployment: Detected unrecoverable event FailedPostStartHook: PostStartHook failed." There is no workaround available.

There is a known issue where the .NET sample fails to start on the arm64 architecture because there is no quay.io/devspaces/dotnet-90 image available for arm64. There is no workaround available.

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