Eclipse Che 7.105.0

Major Enhancements

Allow operator to run in namespaces with enforce=restricted Pod Security Standards

Starting from this release, you can have both the operator and operands running in namespaces with the
pod-security.kubernetes.io/enforce=restricted labels. Learn more about enforcing Pod Security Standards with Namespace Labels from the official Kubernetes documentation.

Allow to specify persistent volume type RWX when using strategy per-user

With DevWorkspace Operator 0.35.0, you can configure the storage access mode for PVCs managed by the DevWorkspace Operator.

apiVersion: controller.devfile.io/v1alpha1
kind: DevWorkspaceOperatorConfig
metadata:
  name: devworkspace-operator-config
  namespace: $OPERATOR_INSTALL_NAMESPACE
config:
  workspace:
    storageAccessMode:
    - ReadWriteMany

With the configuration above, newly created PVCs will have the ReadWriteMany access mode:

Enable Che Server Build Support on s390x Architecture

The che-server component is now built on the s390x architecture, ensuring successful builds on IBM Z running RHEL 9.4 in the upstream.

Bug Fixes

Common PVC cleanup job can be assigned to incorrect node in multi-node cluster

With DevWorkspace Operator 0.35.0, if there are multiple Cloud Developer Environments (CDEs) using a common PVC, and if a running CDE is deleted, the cleanup job pod will always be scheduled on the node the CDE pod was running in. For common PVCs with the ReadWriteOnce access mode, this prevents the Multi-Attach error which caused the cleanup job to be assigned to an incorrect node .

Do not overwrite NODE_EXTRA_CA_CERTS environment variable on the workspace startup

You can use your own CA certificate by specifying the path to the certificate in the NODE_EXTRA_CA_CERTS environment variable. This fix guarantees that the value of the NODE_EXTRA_CA_CERTS environment variable will not be overwritten on the workspace startup.

Non-admin user can't fetch list of workspaces into JetBrains Gateway using Plugin

Previously, if a user was not allowed to list the 'devWorkspace' objects in one of the namespaces, this led to an empty workspace list in the Gateway UI. The defect has been fixed in the v0.0.11 plugin release.

ConfigMap vscode-editor-configurations does not replicate the changes in the namespace

Previously, changes added to the settings.json and extensions.json in the vscode-editor-configurations CM were not applied correctly. The defect has been fixed in this release. Learn more about applying editor configurations in the official documentation.

VS Code OpenShift Toolkit extension does not detect connection on the cluster it is deployed on

Before this release, OpenShift Toolkit extension did not detect a connection on the cluster it is deployed on. The defect has been fixed in this release, and now the connection is displayed correctly:

Token injection fails on workspace restart after expiry

Previously, if the OpenShift user token expired, restarting the workspace did not inject/refresh the new token. The defect has been fixed in this release.

User Dashboard showed wrong devfile content of workspace created from private GitHub repo using SSH URL

Before this release, the wrong devfile content was displayed for workspaces created from a private GitHub repository using SSH URL. The defect has been fixed in this release.