Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Release notes and known issues

Red Hat OpenShift Dev Spaces 3.4

Release notes and known issues for Red Hat OpenShift Dev Spaces 3.4

Robert Kratky

Fabrice Flore-Thébault

Jana Vrbkova

Max Leonov

Red Hat Developer Group Documentation Team

Abstract

Information about new and noteworthy features as well as known issues in Red Hat OpenShift Dev Spaces 3.4.

Making open source more inclusive
Copy link

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.

Chapter 1. About Red Hat OpenShift Dev Spaces
Copy link

Red Hat OpenShift Dev Spaces is a web-based integrated development environment (IDE). OpenShift Dev Spaces runs in OpenShift and is well-suited for container-based development.

OpenShift Dev Spaces provides:

  • an enterprise-level cloud developer workspace server
  • a browser-based IDE
  • ready-to-use developer stacks for popular programming languages, frameworks, and Red Hat technologies

Red Hat OpenShift Dev Spaces 3.4 is based on Eclipse Che 7.58.

1.1. Supported platforms
Copy link

OpenShift Dev Spaces runs on OpenShift 4.10 and 4.11 on the following CPU architectures:

  • AMD64 and Intel 64 (x86_64)
  • IBM Power (ppc64le) and IBM Z (s390x)

Additional resources

1.2. Support policy
Copy link

For Red Hat OpenShift Dev Spaces 3.4, Red Hat will provide support for deployment, configuration, and use of the product.

Additional resources

The main differences between OpenShift Dev Spaces and Eclipse Che are:

  • OpenShift Dev Spaces is built on RHEL8 to ensure the latest security fixes are included, compared to Alpine distributions that take a longer time to update.
  • OpenShift Dev Spaces uses OpenShift OAuth for user login and management.
  • OpenShift Dev Spaces provides a smaller supported subset of plug-ins compared to Che.
  • OpenShift Dev Spaces provides devfiles for working with other Red Hat technologies such as EAP and Fuse.
  • OpenShift Dev Spaces is supported on OpenShift Container Platform, OpenShift Dedicated, and Red Hat OpenShift Service on AWS (ROSA); Eclipse Che can also run on other Kubernetes clusters.

Red Hat provides licensing, packaging, and support. Therefore, OpenShift Dev Spaces is considered a more stable product than the upstream Eclipse Che project.

Chapter 2. New features and enhancements
Copy link

With this update, you can deploy OpenShift Dev Spaces from the fast channel rather than from the default stable channel by running the following command: dsc server:deploy --olm-channel=fast.

Warning

Red Hat support does not extend to OpenShift Dev Spaces instances deployed from the fast channel. The fast channel is for testing release candidates and CI versions of future supported releases. To switch from the fast channel to the stable channel, delete the fast subscription and create a new subscription from the stable channel.

Additional resources

2.2. Support for more devfile components
Copy link

With this update, OpenShift Dev Spaces supports devfile components of types kubernetes and openshift, which reference Kubernetes and OpenShift manifests and include them as part of a workspace. See the devfile v2 specification for more details.

Additional resources

With this update, administrators can configure the service account used for all workspace Pods by adding a .spec.devEnvironments.serviceAccount field in the CheCluster custom resource.

Additional resources

With this update, the recommended extensions from the .vscode/extensions.json file are automatically installed at workspace startup.

Additional resources

2.5. Updates to the sample projects
Copy link

In OpenShift Dev Spaces 3.4, the sample projects provided in the dashboard have changed as follows:

  • Python testing and linting with Flake8 works automatically out of the box.
  • The .NET sample has access to a .NET 6 and 7 runtimes. .NET 3.1 has been removed from the Universal Developer Image (UDI).
  • The CakePHP sample is replaced by a simpler "Hello, World" CLI PHP sample; Xdebug is now included.
  • The Gradle sample has been removed.

Additional resources

2.6. Updated Universal Developer Image
Copy link

In OpenShift Dev Spaces 3.4, the Universal Developer Image (UDI) is updated as follows:

  • Python linting now uses Flake8 instead of Pylint in UI and command line.
  • Dotnet 3.1 is removed.
  • For PHP development: Composer and HTTPd have been removed, Xdebug is now included.
  • Gradle is removed.
  • Maven is updated to the latest RPM version 3.6.2-7.
  • e2fsprogs is updated to the latest RPM version 1.45.6.
  • the Go language server gopls, is upgraded to version 0.10.1.
  • odo is updated to 3.4.0
Tip

To include other tools or runtimes, an administrator can extend or replace the UDI image with one that includes the tools appropriate for your organization and your users' needs. You can refer to the replacement image in the CheCluster custom resource so that users can use the custom image in their devfiles. This will ensure that the tools and runtimes they need are persistent and do not need to be installed on each workspace startup.

Users can also develop their own UDI image(s) and refer to them from their devfiles. This requires publishing the image to a registry that is accessible from their organization’s cluster. However, this approach is less centralized and standardized, and may not scale or perform as well.

Additional resources

With this update, you can use the DevWorkspace tab from the Workspaces menu to view the specification of the DevWorkspace object that defines a workspace.

Additional resources

Chapter 3. Bug fixes
Copy link

Before this update, when workspaces failed to start due to insufficient CPU or memory in available cluster nodes, there was a UI delay in notifying the user. The dashboard Progress tab remained at Waiting for workspace to start until the workspace startup timeout, and only then the error message Failed to open the workspace appeared. With this update, the Dev Workspace Operator aborts workspace startup if it detects an unschedulable condition and then quickly displays the following error message: Failed to open the workspace: Pod is unschedulable: <reasons_and_statuses>.

Additional resources

Before this update, the developer could be logged out unexpectedly because the session expired. With this update, the issue is resolved.

Additional resources

3.3. Fixed legacy OLM CatalogSource pod crashes
Copy link

Before this update, legacy CatalogSource objects used by the Operator Lifecycle Manager (OLM) could enter a crashing state on OpenShift 4.12. This issue affected clusters with [rh-os-devspaces] 3.3 and below with container builds enabled. With this update, the issue is fixed.

Additional resources

Chapter 4. Technology preview
Copy link

Technology Preview features provide early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process. However, these features are not fully supported under Red Hat Subscription Level Agreements, may not be functionally complete, and are not intended for production use. As Red Hat considers making future iterations of Technology Preview features generally available, we will attempt to resolve any issues that customers experience when using these features. See: Technology preview support scope.

None.

Chapter 5. Deprecated functionalities
Copy link

In OpenShift Dev Spaces 3.4, use of the Eclipse Theia editor in workspaces is deprecated. Red Hat will provide limited bug fixes and support for Eclipse Theia in OpenShift Dev Spaces during the current release lifecycle. Eclipse Theia will no longer receive enhancements for OpenShift Dev Spaces and will be removed from OpenShift Dev Spaces in a later release.

Note

Microsoft Visual Studio Code - Open Source is the default editor with air gap support.

Additional resources

Chapter 6. Removed functionalities
Copy link

None.

Chapter 7. Known issues
Copy link

None.

Chapter 8. Frequently asked questions
Copy link

Is it possible to deploy applications to an OpenShift cluster from OpenShift Dev Spaces?
Yes. The user must log in to the OpenShift cluster from their running workspace using oc login.
For best performance, what is the recommended storage to use for Persistent Volumes used with OpenShift Dev Spaces?
Use block storage.
Is it possible to deploy more than one OpenShift Dev Spaces instance on the same cluster?
It is not recommended. This feature is subject to removal in a future release.
Is it possible to install OpenShift Dev Spaces offline (that is, disconnected from the internet)?
Yes. See Installing Red Hat OpenShift Dev Spaces in restricted environments on OpenShift.
Is it possible to use non-default certificates with OpenShift Dev Spaces?
Yes, you can use self-signed or public certificates. See Importing untrusted TLS certificates.
Is it possible to run multiple workspaces simultaneously?
Yes. See Enabling users to run multiple workspaces simultaneously.
What specific changes have been implemented for IBM Power Systems?

The memory limit for some plug-ins has been increased, to give Pods sufficient RAM to run.

Expand
Table 8.1. Example memory limits differences between IBM Power System and other architectures
Plug-inIBM Power SystemOther architectures

Che-Theia editor

2G

512M

OpenShift connector

2.5G

1.5G

Legal Notice
Copy link

Copyright © 2023 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red HatBack to top