Skip to content

Eclipse Che 7.93.0

Compare
Choose a tag to compare
@ibuziuk ibuziuk released this 11 Oct 12:53
· 14 commits to main since this release

Major Enhancements

Add option to deploy operands on the specific cluster nodes

With this release, you can deploy operands (dashboard, server, plugin-registry, etc.) on specific cluster nodes using the dedicated nodeSelector and tolerations CR properties:

    dashboard:
      deployment:
        nodeSelector:
        tolerations:

Ability to create the .gitconfig file from the User Dashboard regardless of the authentication method setup on the cluster

You can now create or import the .gitconfig file from the User Dashboard regardless of the authentication method setup on the cluster:

Screen.Recording.2024-09-26.at.13.10.06.mov

Before this release, it was not possible to create or import a .gitconfig file if you were logged in via LDAP or local authentication. Instead, you had to manually create a dedicated configmap for the a .gitconfig file in their namespace.

Endpoint-specific service for discoverable endpoints

When setting the discoverable: true attribute on a Devfile container component endpoint, a dedicated service will be created and used for the endpoint. For all other endpoints that do not set the discoverable: true attribute, the common workspace service will be used.

The dedicated service created for the endpoint will have a static name, corresponding to the endpoint's name. For instance, a service named http-python will be generated in the example endpoint defined below:

# Example endpoint with discoverable attribute
- exposure: public
  targetPort: 8080
  name: http-python
  protocol: http
  secure: true
  attributes:
    discoverable: true

Documentation for a minimal set of permissions for deploying Eclipse Che on OpenShift

The official documentation defines minimal permissions for installing Eclipse Che on an OpenShift cluster using CLI or web console UI starting from this release.

Bug Fixes

JetBrains IDE-based CDE should not depend on Node.js presence in a user's container

Previously, the tools container of the Cloud Development Environment (CDE) required Node.js to serve the JetBrains IDEA server stub web page. This defect has been fixed in this release.

Dashboard does not show the editors tags

Previously, the editors tags were not correctly displayed on the User Dashboard. The defect has been fixed in this release:

Screenshot 2024-10-10 at 18 05 42

Opening links doesn't work in Visual Studio Code - Open Source ("Code - OSS")

In the Visual Studio Code - Open Source ("Code - OSS") editor, clicking on links within welcome pages and project README files had no effect. This defect has been fixed in this release.

Temporary Storage switch does not work properly

Previously, the 'Temporary Storage' switch was not working correctly on the User Dashboard. The defect has been fixed in this release.

Screenshot 2024-10-10 at 18 10 16

Workspace creation is stopped after clicking Continue in the 'Trust the repository authors' pop-up

Previously if the admin configured allowed URLs for Cloud Development Environments, workspace creation was stopped after a user clicked on the 'Continue' button in the 'Trust the repository authors' pop-up. The defect has been fixed in this release.

The 'Untrusted Repository' pop-up re-appears when OAuth authorization is refused

Before this release, there was a known issue with OAuth authorization and the 'Untrusted Repository' pop-up. When you launched a factory with OAuth setup and refused the OAuth authorization prompt, the pop-up would reappear. The defect has been fixed in this release.

Workspace does not run after refusing OAuth authorization

Previously, if you refused the OAuth authorization the CDE would not start. The defect has been fixed in this release.

che-next-refused-oauth-ws-no-run.webm

Unexpected error message 'No IDE URL after 20 sec during workspace startup'

Before this release, the error message could appear during a Cloud Development Environment (CDE) startup: 'No IDE URL after 20 sec during workspace startup'. The defect has been fixed in this release.

Screenshot 2024-10-10 at 18 02 00