Chapter 1. Release notes
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.
This section documents the most important features and bug fixes in Red Hat CodeReady Workspaces. For the list of CodeReady Workspaces 2.7 release issues, see the Chapter 3, Known issues section.
To deploy applications to an OpenShift cluster from CodeReady Workspaces, users must log in to the OpenShift cluster from their running workspace using
- Having multiple CodeReady Workspaces deployments on the same cluster is not recommended, and the ability to do so may be removed in a future release.
- For best performance, use block storage for Persistent Volumes used with CodeReady Workspaces.
The name of the default CodeReady Workspaces namespace is openshift-workspaces. A user who wishes to use the previous name for the default namespace,
workspaces, needs to note that documentation was updated to reflect the current state.
- For IBM Power Systems (ppc64le), the memory limit for some plug-ins has been increased by up to 1.5G to allow pods sufficient RAM to run. For example, on IBM Power Systems (ppc64le), the Che-Theia editor pod requires 2G; the OpenShift connector pod requires 2.5G. For AMD64 and Intel 64 (x86_64) and IBM Z (s390x), memory requirements remain lower at 512M and 1500M respectively.
CodeReady Workspaces 2.7.1 with a metrics collection bug fix has been released
In CodeReady Workspaces 2.7, CodeReady Workspaces Operator labels were updated to align object labels with the default object labels used by Kubernetes. One of Operator labels was renamed from
However, this information was not updated in CodeReady Workspaces 2.7 service monitor. Due to this, the CodeReady Workspaces 2.7 service monitor could not retrieve the metrics, as they were not exposed from OpenShift Container Platform instances to the telemeter. The bug has been fixed and the service monitor is now fully operational again.
- Upgrade automatically to CodeReady Workspaces 2.7.1 using OLM subscription for all supported OpenShift 4 instances.
For instances on OpenShift 3.11, the upgrade will cause no effect because the telemeter is not supported on this platform.
For additional information about upgrading, follow the Upgrading CodeReady Workspaces chapter of the Installation Guide.
1.1. About Red Hat CodeReady Workspaces
Red Hat CodeReady Workspaces 2.7 provides an enterprise-level cloud developer workspace server and browser-based IDE. CodeReady Workspaces includes ready-to-use developer stacks for some of the most popular programming languages, frameworks, and Red Hat technologies.
This minor release of Red Hat CodeReady Workspaces is based on Eclipse Che 7.26 and offers a number of enhancements and new features, including:
- Improvements to workspace start and overall performance
Bug fixes, such as:
- Signing in to GitHub from a CodeReady Workspaces workspace using the GitHub plug-in fails
Upgrade to CodeReady Workspaces version 2.7 using
crwctlfails on OpenShift Container Platform 3.11
- Plug-in list is empty behind the proxy
- Missing options in source control: git
Debugging of the current file failed to start in the
Plugin and Devfile Registry Updates
CodeReady Workspaces 2.7 is available in the Red Hat Container Catalog. Install it on OpenShift Container Platform, starting at version 3.11, by following the instructions in the Installing CodeReady Workspaces on OpenShift Container Platform 3.11 chapter of the Installation Guide.
CodeReady Workspaces 2.7 is available from the OperatorHub in OpenShift 4.6 and beyond. CodeReady Workspaces 2.7 is based on a new Operator that uses the Operator Lifecycle Manager. This makes the CodeReady Workspaces installation flow simpler and doable without leaving the OpenShift Console.
To install CodeReady Workspaces for OpenShift 4.6 or later, get CodeReady Workspaces from the OperatorHub and follow the Installing CodeReady Workspaces on OpenShift 4 from OperatorHub chapter of the Installation Guide.
1.2. Notable enhancements
1.2.1. Support for OpenShift Container Platform 4.7
In addition to OpenShift 4.6 and 3.11, CodeReady Workspaces 2.7 now supports OpenShift 4.7 on the AMD64 and Intel 64 (x86_64), IBM Z (s390x), and IBM Power Systems (ppc64le) architectures.
1.2.2. Plug-in for a workspace resource monitoring
To allow users to better understand their workspace’s performance, a new plug-in that uses an API call to retrieve information about underlying resources, such as CPU and memory usage and available disk space, is added for every new workspace.
1.2.3. JBoss EAP Extension Pack 2.0 Bootable JAR support
A devfile for EAP XP 2 was added in the previous release of CodeReady Workspaces. This devfile is now available for IBM Power Systems and IBM Z architectures.
1.2.4. Added ability to configure workspace Pod tolerations
This feature adds support for setting Pod tolerations for workspaces, allowing users to specify which nodes workspaces run on. For more details, see the Understanding taints and tolerations chapter in the OpenShift documentation.
1.3. Other enhancements
1.3.1. Automatic plug-in registry validation
A newly added plug-in validation tool checks the correctness of URL values set in the
chePlugins.repositories field of the
settings.json file. After adding a new plug-in registry, the list of plug-ins in the Plug-ins view is refreshed, and if the new plug-in registry is not valid, a user is notified by a warning message. This check is also functional for plug-ins added using the Command palette command
Add plugin registry.
1.3.2. CodeReady Workspaces plug-in registry now includes provider icons
The plugin view now includes the third-party provider icons to better differentiate between languages and providers when browsing available plug-ins.
1.3.3. Faster failure and improved error description in the case of
Creation of workspaces will now fail fast in the case of an underlying
ReplicaSetCreateError, and provide an appropriate message back to the user. Previously in this scenario, a workspace start would eventually timeout with a generic error.
- The error description related to this case were reworded.