Release notes and known issues

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

For Red Hat OpenShift Dev Spaces 3.26, 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 Choose an Editor view on the user dashboard is improved. Editors are now neatly grouped and sorted to provide better usability and a more organized selection process.

This update ensures that you can quickly find and select your preferred development environment from the available grouped options.

With this release, you can set maximum resource limits and requests for workspace containers by using the spec.DevWorkspace.containerResourceCaps field in the CheCluster custom resource (CR). This update ensures that you do not create workspaces with excessive CPU or memory requirements at the devfile level.

With this release, you can rename your workspaces directly from the Overview tab in the dashboard. This update introduces a consistent user experience by using a new reusable copy-to-clipboard component.

You can edit a workspace name when the workspace is in the Stopped or Failed state. The dashboard validates new names for length, naming patterns, and duplicates to ensure accuracy before you save your changes.

With this release, per-user storage error handling is improved through new persistent volume claim (PVC) error detection and guided recovery steps. If a workspace fails to start because the PVC storage is full, you see a clear error message that identifies the workspace name and the root cause.

The guided recovery provides a direct link to the OpenShift Console PVC management view and a YAML snippet to help you expand the PVC manually. These steps ensure that you can resolve storage issues quickly to restart your workspace.

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

For more infomation, see link"https://code.visualstudio.com/updates/v1_104[VS Code release notes].

With this release, the landing page for connecting to a workspace by using VS Code (SSHD) is improved. The update enhances the presentation with better styling and adds copy-to-clipboard functionality for commands and configuration snippets.

The landing page now includes direct links for required tools and authentication. Additionally, the instructions provide guidance for Windows users where applicable, ensuring a smoother connection process across different operating systems.

The DevWorkspace Operator component is updated to version 0.39.0. This version provides important fixes and enhancements to Dev Spaces.

For more information, see the DevWorkspace Operator changelog.

With this release, the Downloading IDE binaries…​ (it can take a few minutes) message is displayed only when it is relevant.

This message no longer appears on the Starting workspace page for the default VS Code editor. This update ensures that you receive accurate information about the workspace startup process and avoids unnecessary confusion. 

With this release, custom logo rendering on the user dashboard is improved. This update resolves an issue where base64-encoded images appeared blurry and ensures that images remain sharp on the loading page.

The dashboard now supports multiple image formats, including JPG, PNG, GIF, WebP, and SVG. Additionally, this update introduces dynamic loader image selection and includes a "Loading…​" fallback for SVG files to ensure a smooth visual experience.

An issue is resolved where project cloning failed when you defined custom getting-started samples by using an SSH URL for the Git repository. Previously, attempting to launch a custom sample with an SSH URL resulted in a 403 error during the cloning process.

With this fix, you can successfully launch custom samples that use SSH URLs. This update ensures a consistent workspace creation flow when you use custom sample configurations.

Before this update, advanced authorization errors displayed an unhelpful "Error [object Object]" message. As a consequence, users could not determine the cause of authorization failures. With this release, the proper authorization error message is displayed. As a result, you receive clear and actionable information about authorization issues.

An issue is resolved where the Save button was not correctly disabled in the User Preferences section of the dashboard. When Git configuration settings are already applied, the Save button is now correctly disabled.

This fix ensures consistent dashboard behavior when you refresh the page or switch between different preference tabs.

Before this update, the Close and Stop button did not always stop the active Dev Workspace. As a consequence, workspaces could continue running after the IDE was closed. With this release, the button behavior is corrected to ensure proper workspace termination. As a result, closing the IDE reliably stops the associated workspace.

Before this update, long-running tasks in terminals did not prevent workspace idle termination. As a consequence, workspaces could shut down while important processes were still executing. With this release, tools running in terminals are properly detected and prevent workspace idling. As a result, long-running terminal tasks complete without interruption.

Red Hat OpenShift Dev Spaces now includes native support for the Kiro editor as a local-to-remote SSH IDE. This update introduces a dedicated editor definition tile in the dashboard, allowing you to connect a local Kiro desktop application directly to running workspaces.

Known issues

The Kiro desktop application (version 0.8.206) might encounter a connection error after you sign in with a Google account. The error message indicates "Too many authentication failures," and logs show that all configured authentication methods failed.

Workaround

Sign in to the Kiro desktop application by using an AWS Builder ID instead of a Google account.

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.