eclipse-che/che 7.82.0

Eclipse Che 7.82.0

on GitHub

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:

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:

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:

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.

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.