Release Notes and Known Issues
Release Notes and Known Issues for Red Hat CodeReady Workspaces 2.15
Robert Kratky
rkratky@redhat.com
Fabrice Flore-Thébault
ffloreth@redhat.com
Jana Vrbkova
jvrbkova@redhat.com
Max Leonov
mleonov@redhat.com
devtools-docs@redhat.com
Abstract
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 CodeReady Workspaces
Red Hat CodeReady Workspaces is a web-based integrated development environment (IDE). CodeReady Workspaces runs in OpenShift and is well-suited for container-based development.
CodeReady Workspaces 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 CodeReady Workspaces 2.15 is based on Eclipse Che 7.42.
1.1. Supported deployment environments
This section describes the availability and the supported installation methods of CodeReady Workspaces 2.15 on OpenShift Container Platform 4.10 4.8, 3.11, and OpenShift Dedicated.
Table 1.1. Supported deployment environments for CodeReady Workspaces 2.15 on OpenShift Container Platform and OpenShift Dedicated
Platform | Architecture | Deployment method |
OpenShift Container Platform 3.11 | AMD64 and Intel 64 (x86_64) |
|
OpenShift Container Platform 4.8 to 4.10 | AMD64 and Intel 64 (x86_64) |
OperatorHub, |
OpenShift Container Platform 4.8 to 4.10 | IBM Z (s390x) |
OperatorHub, |
OpenShift Container Platform 4.8 to 4.10 | IBM Power (ppc64le) |
OperatorHub, |
OpenShift Dedicated 4.10 | AMD64 and Intel 64 (x86_64) | |
Red Hat OpenShift Service on AWS (ROSA) | AMD64 and Intel 64 (x86_64) |
1.2. Support policy
For Red Hat CodeReady Workspaces 2.15, Red Hat will provide support for deployment, configuration, and use of the product.
CodeReady Workspaces 2.15 has been tested on Chrome version 94.0.4606.81 (Official Build) (64-bit).
Additional resources
1.3. Differences between Eclipse Che and Red Hat CodeReady Workspaces
The main differences between CodeReady Workspaces and Eclipse Che are:
- CodeReady Workspaces is built on RHEL8 to ensure the latest security fixes are included, compared to Alpine distributions that take a longer time to update.
- CodeReady Workspaces uses Red Hat Single Sign-On (RH-SSO) rather than the upstream project Keycloak.
- CodeReady Workspaces provides a smaller supported subset of plug-ins compared to Che.
- CodeReady Workspaces provides devfiles for working with other Red Hat technologies such as EAP and Fuse.
- CodeReady Workspaces is supported on OpenShift Container Platform and OpenShift Dedicated; Eclipse Che can run on other Kubernetes clusters.
Red Hat provides licensing, packaging, and support. Therefore, CodeReady Workspaces is considered a more stable product than the upstream Eclipse Che project.
Chapter 2. Notable enhancements
2.1. CodeReady Workspaces 2.15.1 updates to RH-SSO 7.5.1
CodeReady Workspaces 2.15.1 has been updated from including Red Hat Single Sign-On 7.4 to Red Hat Single Sign-On 7.5.1 for two reasons: * The latest update includes all the most recent bug fixes and security updates. * The latest update replaces the deprecated OpenJ9 images with Red Hat build of OpenJDK based images for use with all three supported architectures: AMD64, IBM Z, and IBM Power.
Additional resources
2.2. IntelliJ IDEA Community Edition sample
With this update, a sample is available in the CodeReady Workspaces dashboard for starting a new workspace with IntelliJ IDEA Community Edition in it.
The IntelliJ IDEA Community Edition sample is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/.
Additional resources
2.3. Planned removal of support for the CodeReady Workspaces deployment environments
In Red Hat OpenShift Dev Spaces 3.0 (formerly CodeReady Workspaces), support for the following deployment environments is planned for removal due to the switch to the DevWorkspace Operator:
- OpenShift Container Platform 3.11
- OpenShift Container Platform 4.8
- OpenShift Container Platform 4.9
- Red Hat OpenShift Dedicated 4.8
- Red Hat OpenShift Dedicated 4.9
- Red Hat OpenShift Service on AWS 4.8
- Red Hat OpenShift Service on AWS 4.9
Bug fixes and support are planned through the end of the 2.15.z life cycle. After which, no new feature enhancements are made.
With Red Hat OpenShift Dev Spaces 3.0 (formerly CodeReady Workspaces), the supported deployment environments will be the following: * OpenShift Container Platform 4.10 * Red Hat OpenShift Dedicated 4.10 * Red Hat OpenShift Service on AWS 4.10
Additional resources
2.4. CodeReady Workspaces with the DevWorkspace Operator supports Git LFS
With this update, Git Large File Storage (LFS) is enabled with the DevWorkspace Operator 0.12 or later. The LFS is enabled when you create the workspace by using a devfile to point to a Git repository or when you manually clone a Git repository inside the workspace. To install a CodeReady Workspaces instance with the DevWorkspace Operator, use the Red Hat CodeReady Workspaces - Technical Preview Operator in the OperatorHub.
Additional resources
2.5. Code samples implement the devfile v2 specification
Before this update, code samples implemented the devfile v1 specification. With this update, code samples are implementing the devfile v2 specification.
Additional resources
2.6. Upgrade of the Language Support for Apache Camel extension for Visual Studio Code
Language Support for Apache Camel by Red Hat, the Visual Studio Code extension that adds Apache Camel language support for XML DSL and Java DSL code, is upgraded to 0.1.3.
Additional resources
2.7. Improved performance of the Java and Quarkus extensions for Visual Studio Code
This enhancement improves the startup and runtime performance of the Java and Quarkus extensions for Visual Studio Code in workspaces that load Che-Theia with these extensions. The improved performance is achieved by increasing the CPU limit from 500 MB to 800 MB.
Additional resources
2.8. Tech-Preview
samples in the dashboard
With this update, Technology Preview samples in the dashboard are now labelled with Tech-Preview
to differentiate them from the samples that have full Red Hat support.
Tech-Preview
samples are Technology Preview features only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/.
Additional resources
2.9. Removal of the crwctl workspace:
and crwctl auth:
commands
In CodeReady Workspaces 2.15, the crwctl workspace:
and crwctl auth:
commands are removed. You can use the CodeReady Workspaces dashboard instead. Bug fixes and support are provided through the end of the CodeReady Workspaces 2.14 life cycle. After which, no new feature enhancements are made.
Additional resources
2.10. OpenJDK replaces JVM on IBM Power and IBM Z
Before this update, Eclipse OpenJ9 was the Java SE implementation for containers targeting IBM Power (ppc64le) and IBM Z (s390x) OpenShift clusters. With this update, the OpenJ9 JVM in the OpenShift containers for IBM Power (ppc64le) and IBM Z (s390x) is replaced by the Red Hat build of OpenJDK. Existing CodeReady Workspaces installations, on update to 2.15.1, switch over to use OpenJDK in the Java 8 and 11 sidecar images rather than the OpenJ9 ones. Customers whose devfiles reference the OpenJ9-based containers must edit their devfiles and replace "-openj9-rhel8" with "-rhel8" to continue to receive security updates. See also CRW-2785.
Additional resources
2.11. CodeReady Workspaces 2.15.1 availability on OpenShift Container Platform 4.10
With this update, CodeReady Workspaces 2.15.1 will be available through OperatorHub on OpenShift Container Platform 4.10.
Additional resources
Chapter 3. Bug fixes
3.1. CodeReady Workspaces with the CodeReady Workspaces server engine and GitHub OAuth successfully starts devfile v2 workspaces
Before this update, when a CodeReady Workspaces instance was configured with the CodeReady Workspaces server engine and GitHub OAuth, CodeReady Workspaces failed to start a workspace using the devfile v2 specification. With this update, a CodeReady Workspaces instance configured with the CodeReady Workspaces server engine and GitHub OAuth successfully starts a workspace using the devfile v2 specification.
Additional resources
Chapter 4. Known issues
4.1. Debugging cannot be activated in Go workspaces on IBM Z and IBM Power
On IBM Z and IBM Power, the debugging features cannot be activated in the Go workspace in CodeReady Workspaces 2.15. Delve, the required debugger for the Go programming language, is not available for these platforms. An attempt to activate this feature results in the Failed to continue
error message. This issue has no workaround.
Additional resources
4.2. Language server features are not preinstalled in Go workspaces
Golang based workspaces do not include basic language server features such as code autocompletion.
Workaround
- Run the CodeReady Workspaces instance in a non-restricted environment.
- Install the required module by using the Install button in the IDE dialog box.
Additional resources
4.3. Attempts to clone a workspace from a Quick Add sample result in an error under the single-host
strategy
When using the single-host
strategy for workspace exposure, attempting to clone a workspace from a Quick Add sample results in an error. There is currently no workaround for this issue.
Additional resources
4.4. Workspace creation fails on unstable networks
CodeReady Workspaces might fail to create a workspace when the network is unstable. CodeReady Workspaces displays an error such as the following: Failed to run the workspace: "Waiting for pod 'workspace9fbid1gnx7273d47.maven-545f8c9cf4-hw79f' was interrupted." This issue has no workaround.
Additional resources
4.5. Unsupported devfiles on IBM Z and IBM Power
The following devfiles are not supported on IBM Z and IBM Power:
- EAP for OpenJDK 8
- .Net
- Fuse
- Apache Camel K by Red Hat
Workaround
- Do not use unsupported languages on IBM Z and IBM Power.
Additional resources
4.6. No delegateCommandHandler error for Java with the JBoss EAP 7.3 devfile
A workspace using Java with the JBoss EAP 7.3 devfile fails with the following error message: No delegateCommandHandler for vscode.java.startDebugSession
. There is no workaround for this issue.
Additional resources
4.7. No display for a task after a networking issue
When a task is running and there is some networking issue, the terminal window is cleared and contains no text. Even when the connection is restored, the terminal remains empty and loading. There is no workaround for this issue.
Additional resources
4.8. The OpenShift Connector plug-in fails to deploy an application in a restricted environment
The OpenShift Connector plug-in fails to deploy because of the inability to access the odo
image in the disconnected environment. There is no workaround for this issue.
Additional resources
4.9. The DEBUG configuration is missing
The DEBUG panel displays No Configurations in the drop-down list because no configurations are loaded.
Workaround
- Refresh the page to display the debug configurations.
Additional resources
4.10. Namespace restriction for OpenShift Dedicated and ROSA
Currently, there is a restriction for OpenShift Dedicated and ROSA: CodeReady Workspaces must not be deployed to the openshift-workspaces
namespace.
Workaround
- Use another namespace when deploying CodeReady Workspaces on OpenShift Dedicated and ROSA.
Additional resources
4.11. The OpenShift Connector plug-in does not allow the creation of a new component on IBM Power
On IBM Power, the list of supported image streams is missing, which causes component creation to fail. There is currently no workaround for this issue.
Additional resources
4.12. Upgrading a CodeReady Workspaces instance with the Dev Workspace engine enabled requires manual steps
Currently, upgrading a CodeReady Workspaces instance with the Dev Workspace engine enabled requires the following manual steps as a workaround:
Workaround
-
Unsubscribe the CodeReady Workspaces Operator from the
latest
channel. -
Remove the
Dev Workspace Controller
namespace. -
Subscribe the CodeReady Workspaces Operator to the
tech-preview-latest-all-namespaces
channel.
Support for deploying CodeReady Workspaces 2.15 with the Dev Workspace engine is available as a Technology Preview feature for OpenShift Container Platform 4.8. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not fully function. Red Hat does not suggest using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
Additional resources
4.13. The Image Puller does not work with the tech-preview-latest-all-namespaces
channel
Currently, when using OperatorHub to install CodeReady Workspaces with the Dev Workspace engine, you cannot enable the Image Puller. The Image Puller currently does not work with the tech-preview-latest-all-namespaces
channel.
Workaround
-
Fetch the standalone CodeReady Workspaces
imagepuller-rhel8
image and use it manually to perform image pulls across the cluster.
Additional resources
4.14. The command Configure Apache Web Server DocumentRoot
does not work in the Cake-php
sample project on IBM Power
When using the Cake-php
sample, the Configure Apache Web Server DocumentRoots
task fails with the following error:
error sed: couldn't open temporary file /etc/httpd/conf/sedSgv1Z4: Permission denied
There is currently no workaround for this issue.
Additional resources
4.15. Empty page after the user session expires
Currently, a CodeReady Workspaces instance might display an empty page after the user session expires. There is currently no workaround for this issue.
Additional resources
4.16. Empty dashboard after a server error
Currently, the dashboard of a CodeReady Workspaces instance might display an empty page after a server error. There is currently no workaround for this issue.
Additional resources
Chapter 5. Frequently asked questions
- Is it possible to deploy applications to an OpenShift cluster from CodeReady Workspaces?
-
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 CodeReady Workspaces?
- Use block storage.
- Is it possible to deploy more than one CodeReady Workspaces instance on the same cluster?
- It is not recommended. This feature is subject to removal in a future release.
- Is it possible to install CodeReady Workspaces offline (that is, disconnected from the internet)?
- Yes. See Installing CodeReady Workspaces in restricted environments.
- Is it possible to use non-default certificates with CodeReady Workspaces?
- Yes, you can use self-signed or public certificates. See Importing untrusted TLS certificates.
- Is it possible to run multiple workspaces simultaneously?
- Yes. See Configuring the number of workspaces that a user can run.
- 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.
Table 5.1. Example memory limits differences between IBM Power System and other architectures
Plug-in IBM Power System Other architectures Che-Theia editor
2G
512M
OpenShift connector
2.5G
1.5G