Eclipse Che 7.82.0
Major Enhancements
The 'registry.devfile.io' registry used by default in Eclipse Che
With this release, the devfile registry hosted at registry.devfile.io is used by default for the Getting Started samples:
![Screenshot 2024-03-01 at 11 53 10](https://private-user-images.githubusercontent.com/1461122/309236062-f4fa2bdf-99de-4e75-86bf-a9a41ff0bf56.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ3NzUwNDAsIm5iZiI6MTcyNDc3NDc0MCwicGF0aCI6Ii8xNDYxMTIyLzMwOTIzNjA2Mi1mNGZhMmJkZi05OWRlLTRlNzUtODZiZi1hOWE0MWZmMGJmNTYucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgyNyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MjdUMTYwNTQwWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9Y2UwNzA4NjI2MmEyZTlmZTBmOTUyYmYyNzMwZjQ1OTI2ZTU5NDU4NDQ3YzY2NzBmODY0OGU3NjA3OTQ1NWFkYSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.MV_3b8UGyVq_rTEJEE5OE2gEYR92oXnI6YYcVuBnoLY)
The administrator can still enable the embedded devfile registry using the disableInternalRegistry
field in the CheCluster custom resource:
devfileRegistry:
disableInternalRegistry: false
Support for running Che-Code in containers based on Red Hat Universal Base Image 9
Previously, the Che-Code
editor failed to start in the Red Hat Universal Base Image 9. With this release, this issue is fixed and you can now explicitly reference those images in the components
section of a devfile:
schemaVersion: 2.2.2
metadata:
name: ubi9-minimal-demo
components:
- name: tools
container:
image: registry.access.redhat.com/ubi9-minimal:9.3-1552@sha256:582e18f13291d7c686ec4e6e92d20b24c62ae0fc72767c46f30a69b1a6198055
args: ['tail', '-f', '/dev/null']
endpoints:
- exposure: public
name: nodejs
protocol: http
targetPort: 3000
memoryLimit: 2Gi
memoryRequest: 256Mi
mountSources: true
attributes:
controller.devfile.io/merge-contribution: true
Configuring the number of replicas for operand deployments using HorizontalPodAutoscaler (HPA)
Starting from this release, you can configure the number of replicas for operands using HorizontalPodAutoscaler (HPA):
apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
metadata:
name: scaler
namespace: {operator-namespace}
spec:
scaleTargetRef:
apiVersion: apps/v1
kind: Deployment
name: __<deployment_name>__
...
The __<deployment_name>__
in the snippet above corresponds to one of the following deployments:
che-server
che-gateway
dashboard
plugin-registry
devfile-registry
Find more details about the HPA setup in the official documentation.
Enabling fuse-overlayfs for Podman in the Cloud Development Environment
By default, the Universal Developer Image (UDI) contains Podman and Buildah which you can use to build and push container images within a Cloud Development Environment (CDE). However, Podman and Buildah in the UDI are configured to use the vfs
storage driver which does not provide copy-on-write support. For more efficient image management, you can use the fuse-overlayfs
storage driver which supports copy-on-write in rootless environments.
Find more details about fuse-overlayfs
configuration in the official documentation.
Devfile walkthrough VSX extension available by default
With this release, the Devfile Walkthrough VSX extension is available by default in the Cloud Development Environment for the Che-Code
editor:
![Screenshot 2024-03-01 at 12 47 10](https://private-user-images.githubusercontent.com/1461122/309249170-31546500-a638-49b7-a2a3-1d03847ca8e7.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ3NzUwNDAsIm5iZiI6MTcyNDc3NDc0MCwicGF0aCI6Ii8xNDYxMTIyLzMwOTI0OTE3MC0zMTU0NjUwMC1hNjM4LTQ5YjctYTJhMy0xZDAzODQ3Y2E4ZTcucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgyNyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MjdUMTYwNTQwWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NDFlODJjZGFhZmE0ZjY3ZTkwMWMxYzYwMDk2ZGI5MTMxN2FhMTkzMWM4Zjc2Y2Y2ZThjMjM2YTYzNWM1Y2ZkNiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.teZzaAzOliossZf63J1QL-5dG6eUKB615y7eTHYxGTU)
Allow overriding the editor's image through the URL parameter
With this release, you can override the editor's image using a dedicated URL parameter when starting a Cloud Development Environment. Here are some examples:
#https://github.com/eclipse-che/che-docs?editor-image=quay.io/che-incubator/che-code:next
#https://github.com/eclipse-che/che-docs?che-editor=che-incubator/che-code/latest&editor-image=quay.io/che-incubator/che-code:next
Find more details about the editor-image
URL parameter in the official documentation.
Major Bug fixes
Empty Workspace uses the/home/user
directory instead of /projects
by default in the terminal
Previously, there was an issue affecting projects created in/cloned into an empty workspace when the default folder for the projects was the /home/user
directory instead of /projects
. Due to this, the changes were not saved after workspace restart. The issue has been fixed in this release:
![Screenshot 2024-03-01 at 15 34 24](https://private-user-images.githubusercontent.com/1461122/309293002-96b30327-fde8-4fb6-9415-79a6a41fa9e1.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ3NzUwNDAsIm5iZiI6MTcyNDc3NDc0MCwicGF0aCI6Ii8xNDYxMTIyLzMwOTI5MzAwMi05NmIzMDMyNy1mZGU4LTRmYjYtOTQxNS03OWE2YTQxZmE5ZTEucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgyNyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MjdUMTYwNTQwWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YjYwMjE3NDlmMjU1N2QyNjkwMGYyY2U2NTA4NTlmNmQxN2E5ZTk2NTczMWViYzdlZDhlZTQ3YTgxOTllMWFmMSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.z0wWuG06idPltEztQcPUW6Qolvjn0OYclPxdbH1m9Co)
Error is not meaningful when workspace startup fails because of an exceeded route quota
Before this release, when a workspace failed to start due to a quota issue, no meaningful error was displayed, and the startup failed with a timeout. Now there is an explicit error when workspace startup is forbidden due to an exceeded quota:
Failed to set up networking for workspace: services "workspace82736d3c797e4150-service" is forbidden: exceeded quota: resource-quota-services, requested: count/services=1, used: count/services=1, limited: count/services=1
Documentation contains outdated instructions for "Configuring workspaces nodeSelector"
Outdated procedures for the nodeSelector
and tolerations configuration have been fixed in this release and the updated instructions are now available in the official documentation.
Unexpected workspace restart due to scale down of a replicaset
The issue related to an unexpected workspace restart due to the scale down of a replicaset has been fixed in this release.
Cannot revoke Authorization - OAuth token for the user was not found
The bug related to revoking the GitHub Authorization has been fixed in this release. Now all the OAuth tokens are retrieved from the Kubernetes secrets explicitly and not from memory as it used to be beforehand.
![Screenshot 2024-03-01 at 16 43 44](https://private-user-images.githubusercontent.com/1461122/309312286-145984a3-1801-41c8-bd88-b5c68e23fde8.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ3NzUwNDAsIm5iZiI6MTcyNDc3NDc0MCwicGF0aCI6Ii8xNDYxMTIyLzMwOTMxMjI4Ni0xNDU5ODRhMy0xODAxLTQxYzgtYmQ4OC1iNWM2OGUyM2ZkZTgucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgyNyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MjdUMTYwNTQwWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NTEwNjkxNDAzNTQ1NjJhMDc4NjMxYTJmMTM0YmI5Yjc3MjA0YjFkOWM3MzM3OTRkYTQ0ZTVhNWM0MGFkM2M3ZSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.82hpFlPxu87nFIauOcLmEcsNbsouKqvy48DaronSnNw)
Devfile error on starting a workspace from a repository hosted on Bitbucket Server
Before this release, workspace startup from a private repository hosted on Bitbucket Server with a manually added Personal Access Token (PAT) failed with the following error: Failed to create the workspace: Cannot build factory with any of the provided parameters. Please check parameters correctness, and resend query.
With this release, the issue is fixed.
Opening a workspace from a repository hosted on Bitbucket Server integrated with OAuth2 leads to an error when credentials are not available
Previously, some SCM providers like BitBucket Server decode the callback URL in the response, which resulted in an IllegalArgumentException error. With this release, the issue is fixed.