Skip to content

Eclipse Che 7.64.0
Compare
Choose a tag to compare
@l0rd l0rd released this 04 May 10:36
· 204 commits to main since this release
7.64.0
f5192cc

Major Enhancements

Che URL parameter to configure a specific container image

A new parameter, image, let developers specify the main Che workspace image in the workspace URL. It allows to specify a specific container without the need to add devfile in the git repository (a universal developer image container will be used instead). If a devfile is present the image parameter allows to replace the devfile first container component image.

image

Automatically set user and email in git configuration when Git service integration is configured

If Git service OAuth has been setup by Che administrator, or if a user has configured a Git service Personal Access Token secret in his namespace, then git is automatically configured with the right name and email. Developer can run git commit without the need to to configure git.

image

A warning is displayed in Git services preferences when revoking authorization to Eclipse Che OAuth from GUI is not supported

Revoking the authorization granted to the Eclipse Che OAuth appliction from the user preferences is only supported for GitHub. Authorization for other Git services is shown in the preferences panel but it's not possible to revoke it from there. A warning has been added to explain that to the users.

image

A new VS Code menu item to open a Terminal in a specific container has been added

It's now simpler to open a Terminal in a specific container. The command Create New Terminal to DevWorkspace Container has been renamed Create New Terminal (Select a Container) and the command has been added in the Terminal menu and in the Terminal's context menu.

image

Support the permission specification for files auto-mounted with ConfigMaps and Secrets

Eclipse Che automatically mounts as files in workspace containers ConfigMaps and Secrets having some specific annotations. The mounted file permissions was not configurable and was set to 0644. This new feature allows the specification of the file permission using the annotation controller.devfile.io/mount-access-mode. This is useful for example, to mount a ConfigMap as an executable script that can be run from within the container.

image

Set the developer namespace in workspaces .kube/config current context

A ~/.kube/config is generated at workspace startup with the developer credentials. The developer namespace was not specified in the current context of the configuration file. As a consequence tools in the development environment using the Kubernetes API may have unpredictable behaviors. This has been addressed in the release and the generated ~/.kube/config contain the namespace.

image

Support ServiceAccount token volume projection

The ServiceAccount token mounted in workspaces Pods can now be specified as a projected ServiceAccount token. This allows to set the audience, the mountPath and the expirationSeconds of the token and enable federation scenarios such as GCP workload identity federation. Projected tokens properties can be specified in a CheCluster CR:

spec:
  devEnvironments:
    serviceAccountTokens:
      - name: <name>
        mounthPath: <mount-path>
        audience: <audience>
        expirationSeconds: <expiration>
        path: <path>

Support multiple postStart events in Devfiles

Eclipse Che failed to load Devfiles that had more than one postStart event. This has been addressed in this release and multiple events are now supported. Specifying composites commands as postStart event is still not supported.

Here is a Devfile example with 2 commands used as postStart events:

schemaVersion: 2.1.0
metadata:
  name: multi-post-start
components:
  - name: tools
    container:
      image: quay.io/devfile/universal-developer-image
commands:
  - id: first-command
    exec:
      component: tools
      commandLine: "echo first command"
  - id: second-command
    exec:
      component: tools
      commandLine: "echo second command"
events:
  postStart:
    - first-command
    - second-command

Removed Functionalities

Removal of the Che-Theia editor

The definition of the Che-Theia editor has been removed from Eclipse Che plugin registry. As a consequence it's not visible from Eclipse Che dashboard and it's not possible to reference its ID (eclipse/che-theia/latest or eclipse/che-theia/next) in a .che-editor.yaml or as a URL parameter.

image

Major Bug Fixes

Fixed Eclipse Che server image vulnerabilities

Some Eclipse Che server dependencies have been updated to address the vulnerabilities found through Trivy image scan.

Assets 2
Loading