Eclipse Che 7.81.0
Major Enhancements
Replication of Secrets, ConfigMaps, and PersistentVolumesClaims in all user namespaces
With this release, the administrator can configure Secrets, ConfigMaps, and PersistentVolumesClaims that will be replicated in the namespaces of all users. You can therefore share certificates, secrets, and configuration files across all the users.
For example, creating the following ConfigMap makes Maven's settings.xml
file available in the Container Development Environment (CDE) of all the users:
kind: ConfigMap
apiVersion: v1
metadata:
name: user-settings-xml
namespace: {prod-namespace}
labels:
app.kubernetes.io/part-of: che.eclipse.org
app.kubernetes.io/component: workspaces-config
annotations:
controller.devfile.io/mount-as: subpath
controller.devfile.io/mount-path: /home/user/.m2
data:
settings.xml: |
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 https://maven.apache.org/xsd/settings-1.0.0.xsd">
<localRepository>/home/user/.m2/repository</localRepository>
<interactiveMode>true</interactiveMode>
<offline>false</offline>
</settings>
Find more about the procedure in the official documentation and the demo video.
Allow pod-overrides for volumes and container-overrides for volumeMounts in Devfiles
With this release, you can use pod and container overrides for volumes and volumeMounts in the Devfile definition.
For example, you can add a CSI volume with the SharedSecret to a pod or container in the Container Development Environment (CDE):
schemaVersion: 2.2.2
attributes:
controller.devfile.io/storage-type: per-workspace
metadata:
name: pod-overrides-example
attributes:
pod-overrides:
spec:
volumes:
- csi:
driver: csi.sharedresource.openshift.io
readOnly: true
volumeAttributes:
sharedSecret: my-share
name: my-csi-volume
components:
- name: workspace
attributes:
container-overrides:
volumeMounts:
- mountPath: /etc/my-csi-volume
name: my-csi-volume
readOnly: true
container:
...
Prevent starting workspaces based on SSH URLs if no SSH keys are configured
With this release, you can not start workspace based on SSH URLs until you configure the SSH keys in the User Dashboard:
download.mov
Major Bug fixes
"Conflict detected" error during Gitconfig name and email update
Before this release, updating the name and email in the Gitconfig could result in the Conflict detected
error:
The UX defect has been fixed in this release, and you can update the name and email without errors:
Screen.Recording.2024-01-10.at.12.49.55.mov
"Route and path matches, but all pods are down" error during workspace startup
A sporadic defect resulting in the "Route and path matches, but all pods are down" error during workspace startup has been fixed in this release.
![image](https://private-user-images.githubusercontent.com/606959/279319819-03eeedda-96ad-422d-a929-ba3c0165f7fc.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ3NjkwMzAsIm5iZiI6MTcyNDc2ODczMCwicGF0aCI6Ii82MDY5NTkvMjc5MzE5ODE5LTAzZWVlZGRhLTk2YWQtNDIyZC1hOTI5LWJhM2MwMTY1ZjdmYy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODI3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgyN1QxNDI1MzBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1hOGU2NzdmYjNiMzc3NjMwMDlhZTBmNTRmMTFiNTNjMjMyZTkyNzQzMDU3NjE1ZThhNDc5NzViNzEwOGU2MjFkJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.Oi1O4o7YcFul9D6KLFtZmaIjicTPDyd48BX2sNUdW2s)
Operator gets stuck updating endpoint URLs whose hostnames are too long
Before this release, there was a defect related to the update of endpoint URLs whose hostnames were too long. This resulted in the operator getting stuck in a loop. With this release, the issue is fixed.
Length limitation for auto-generated workspace names
Before this release, workspaces started from repositories with names longer than 63 characters failed due to the RFC 1035 Label Names restriction. The issue has been fixed in this release and auto-generated workspace names are trimmed to be compatible with the standard.