3.16.1 Release notes and known issues

Red Hat OpenShift Dev Spaces 3.16

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

Jana Vrbkova

jvrbkova@redhat.com

Red Hat Developer Group Documentation Team devtools-docs@redhat.com

Legal Notice

Abstract

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

Making open source more inclusive

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

Red Hat OpenShift Dev Spaces provides web-based development environments on Red Hat OpenShift with an enterprise-level setup:

Cloud Development Environments (CDE) server
IDEs such as Microsoft Visual Studio Code - Open Source and JetBrains IntelliJ IDEA Community (Technology Preview)
Containerized environments with popular programming languages, frameworks, and Red Hat technologies

Red Hat OpenShift Dev Spaces is well-suited for container-based development.

Red Hat OpenShift Dev Spaces 3.16 is based on Eclipse Che 7.90.

1.1. Supported platforms

OpenShift Dev Spaces runs on OpenShift 4.12–4.16 on the following CPU architectures:

AMD64 and Intel 64 (x86_64)
IBM Z (s390x)

The following CPU architecture requires Openshift 4.13-4.16 to run OpenShift Dev Spaces:

IBM Power (ppc64le)

Additional resources

1.2. Support policy

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

Additional resources

OpenShift Dev Spaces life-cycle and support policy.

1.3. Differences between Red Hat OpenShift Dev Spaces and Eclipse Che

There are some differences between Red Hat OpenShift Dev Spaces and the upstream project on which it is based, Eclipse Che:

OpenShift Dev Spaces is supported only on Red Hat OpenShift.
OpenShift Dev Spaces is based on Red Hat Enterprise Linux and is regularly updated to include the latest security fixes.
OpenShift Dev Spaces provides getting-started samples supported in the air-gap mode with languages and technologies such as Quarkus, Lombok, NodeJS, Python, DotNet, Golang, and C/C++. Community samples are available at the Devfile registry page.
OpenShift Dev Spaces uses OpenShift OAuth for user login and management.

Red Hat provides licensing and packaging to ensure enterprise-level support for OpenShift Dev Spaces.

Chapter 2. New features and enhancements

None.

Chapter 3. Bug fixes

3.1. Extension 'ms-python.python' CANNOT use API proposal: terminalShellIntegration

Before this release, installing the latest Python extension (v2024.14.0) would fail with the following error message: "Extension 'ms-python.python' CANNOT use API proposal: terminalShellIntegration". With this release, the issue is fixed

Additional resources

CRW-7201

3.2. Opening links not possible in the Visual Studio Code - Open Source ("Code - OSS")

Before this release, it was not possible to open links in Visual Studio Code - Open Source ("Code - OSS"). With this release, the issue has been fixed.

Additional resources

CRW-7247

Chapter 4. Technology Preview

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

None.

Chapter 6. Removed functionalities

None.

Chapter 7. Known issues

7.1. OpenShift Welcome page and Ansible content creator page fail to load

There is a known issue affecting workspaces using the Ansible sample and a self-signed TLS certificate. The OpenShift Welcome and the Ansible content creator tabs are empty and the following message appears: "Error loading webview: Error: Could not register service worker: SecurityError: Failed to register a ServiceWorker for scope." There is a workaround available.

Workaround

Add the self-signed TLS certificate to the browser’s trusted root authority by following this procedure.

Additional resources

CRW-7252

7.2. Issues with starting a new workspace from a URL that points to a branch of a repository that doesn’t have a devfile

There is a known issue affecting repositories without a devfile.yaml file. If you start a new workspace from a branch of such repository, the default branch (e.g. 'main') is used for project cloning instead of the expected branch.

Additional resources

CRW-6860

7.3. Refresh token mode causes cyclic reload of the workspace start page

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.

Additional resources

CRW-6859

7.4. FIPS compliance update

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:

Required cluster and operator updates

Update your Red Hat OpenShift Container Platform installation to the latest z-stream update for 4.11, 4.12, or 4.13 as appropriate. If you do not already have FIPS enabled, you will need to uninstall and reinstall.

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

Golang compiler in UDI image

The Universal Developer Image (UDI) container includes a golang compiler, which was built without the CGO_ENABLED=1 flag. The check-payload scanner ( https://github.com/openshift/check-payload ) will throw an error, but this can be safely ignored provided that anything you build with this compiler sets the correct flag CGO_ENABLED=1 and does NOT use extldflags -static or -tags no_openssl.

The resulting binaries can be scanned and should pass without error.

Statically linked binaries

You can find statically linked binaries not related to cryptography in these two containers:

code-rhel8
idea-rhel8.

As they are not related to cryptography, they do not affect FIPS compliance.

Helm support for FIPS

The UDI container includes the helm binary, which was not compiled with FIPS support. If you are in a FIPS environment do not use helm.

Additional resources

CRW-4598

7.5. Debugger does not work in the .NET sample

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

Workaround

Use a different image from the following sources:
- Custom UBI-9 based Dockerfile
- devfile.yaml

Additional resources

CRW-3563

Chapter 8. Frequently asked questions

Is it possible to deploy applications from OpenShift Dev Spaces to an OpenShift cluster?: OpenShift user token is automatically injected into workspace containers which makes it possible to run oc CLI commands against OpenShift cluster.
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?: Only one OpenShift Dev Spaces instance can be deployed per cluster.
Is it possible to install OpenShift Dev Spaces offline (that is, disconnected from the internet)?: See Installing Red Hat OpenShift Dev Spaces in restricted environments on OpenShift.
Is it possible to use non-default certificates with OpenShift Dev Spaces?: You can use self-signed or public certificates. See Importing untrusted TLS certificates.
Is it possible to run multiple workspaces simultaneously?: See Enabling users to run multiple workspaces simultaneously.

Legal Notice

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.

3.16.1 Release notes and known issues