Major Enhancements
Security best practices
With this release, the security best practices for Eclipse Che have been contributed to the official documentation.
Warning message when tracker can not ping machine-exec
When the activity tracker extension could not ping the idler service, there was no user-facing error message displayed. This could cause a situation where your Cloud Development Environment (CDE) is terminated due to the idler, even when you are actively using your CDE. With this release, an error notification warns you when the idler service cannot be reached.
Bug Fixes
Custom editor is not resolved from .che if SSH url is used
Previously, if you started a CDE created with a project with a .che/che-editor.yaml file and used SSH for cloning, the editor in the .che/che-editor.yaml file was not resolved. This issue is fixed in this release.
Add SSH agent postStart event only if SSH key has a passphrase & experimental features enabled
Before this release, if you configured a secret containing a SSH key for git operations, you could provide an SSH passphrase as well. By providing the SSH passphrase in the secret, you could clone and push to the git repository without re-entering the passphrase. This feature caused starting CDE from certain sample projects from the devfile.io registry to fail.
Starting from this release, enabling the SSH passphrase feature requires the admin to set the config.enableExperimentalFeatures field to true in the Che-owned DevWorkspaceOperatorConfig:
apiVersion: controller.devfile.io/v1alpha1
kind: DevWorkspaceOperatorConfig
metadata:
name: devworkspace-config
namespace: eclipse-che
config:
enableExperimentalFeatures: true
Fixed NetworkPolicy podSelector documentation
The previous Configuring network policies documentation contained a network policy that prevented you from creating Cloud Development Environments (CDEs) from sample projects. This issue is fixed in this release.
Logout button on Che dashboard does not work
There was an issue where you were not able to log out after clicking on the "Logout" button. This issue is fixed in this release.
Increase memory limit for the Dev Workspace Operator to 5Gi
The memory limit for the devworkspace-controller-manager-* pod was increased to 5Gi.
Launching a workspace using .devfile.yaml file from Gitlab repository hosted internally fails
Before this release, it was not possible to create Cloud Development Environments (CDEs) from a .devfile within an internally hosted Gitlab repository. With this release, the issue is fixed.