Skip to content

Eclipse Che 7.66.0
Compare
Choose a tag to compare
@l0rd l0rd released this 12 May 11:13
· 201 commits to main since this release
7.66.0
931c6d2

Major Enhancements

Support customizing developer user roles in Che provisioned namespaces

The permissions granted to a user on their Che provisioned namespace are now configurable. This allows the user to create some objects in his namespace that might be needed for their development work. For example: create Kafka or KafkaTopic Custom Resources.

To configure these permissions an administrator has to create the Kubernetes ClusterRole and ClusterRoleBinding and specify them in the CheCluster Custom Resource:

spec:
(...)
  components:
    cheServer:
+      clusterRoles: ${USER_ROLES}
(...)
  devEnvironments:
    user: 
+      clusterRoles: ${USER_ROLES}

Support specifying the Ingress Class Name for Eclipse Che gateway

In addition to the specification of the gateway annotations, Eclipse Che now allows the specification of the IngressClassName field. This is critical as the kubernetes.io/ingress.class annotation on the Ingress has been deprecated. The IngressClassName can be specified in CheCluster networking:

spec:
(...)
  networking:
+    ingressClassName: ${CLASS_NAME}

Update monitoring docs to use the in-cluster monitoring stack Backported to 7.64

The section Configuring Observability of the Eclipse Che documentation has been updated with the instructions to use OpenShift built-in monitor stack instead of template-based Prometheus + Grafana installation.

Report more information when workspace start times out

When a user's workspace fails to start due to timeout Eclipse Che is now providing more information to help diagnose issues with workspace start -- the workspace may fail due to timing out on e.g. "preparing routes" or "waiting on editor to start" for instance.

$ kubectl get devworkspace inventory-quarkus
NAME                DEVWORKSPACE ID             PHASE    INFO
inventory-quarkus   workspace10330798d5bb4963   Failed   DevWorkspace failed to progress past step 'Waiting for workspace deployment' for longer than timeout (300s)

Support Git SSH protocol for starting workspaces

It's now possible to open a workspace with URLs that use the SSH protocol. Before only URLs using the HTTP protocol were supported.

image

⚠️ The support for the Git protocol is still limited as Devfiles in the git repository will be ignored.

Major Bug Fixes

VS Code's Webview functionality should work when the browser is behind the proxy Backported to 7.64

VS Code Webview functionality, used in many extensions, did not render correctly in an air gap scenarios. This was due to the code running in the user browser that tried to download static resources from the public Internet: it failed if the user laptop was behind a proxy. To address the problem we have patched Che VS Code fork to the serve those resources from the VS Code server that runs in the Kubernetes cluster and that should be whitelisted in the proxy configuration.

Assets 2
Loading