Releases: eclipse-che/che
Eclipse Che 7.59.0
Major Enhancements
Add support for devfile kubernetes and openshift components (backported to v7.58)
Eclipse Che now supports devfile components of type kubernetes and openshift. That allow to reference Kubernetes and OpenShift manifests in a devfile and include them as part of the workspace. Devfile components of type volume and container were already supported, components of type image are not supported yet.
Allow configuring workspace start timeout via CheCluster spec
The timeout to consider workspaces startup as failed was hardcoded to 5 minutes and could not be changed by administrators. With this new feature Che administrators can specify the workspaces startup timeout in the CheCluster custom resource.
Allow specify workspace pods schedulerName via CheCluster spec
Before, the Kubernetes scheduler that managed Che workspaces was always the default one. Now Che administrators can specify an alternative Kubernetes scheduler using the CheCluster custom resource.
Backported to 7.58
Allow configuring ephemeral storage strategy in CheCluster
It's now possible to specify ephemeral as the default storage strategy for every workspace through the CheCluster custom resource.
Eclipse Che 7.58.0
Major Enhancements
Auto-install VS Code extensions specified in `.vscode/extensions.json`
Recommended extensions in file .vscode/extensions.json are automatically installed by che-code at workspace startup. Before the developer get prompted to install them. This is the behavior we had in che-theia as well.
Use a pre-created ServiceAccount for workspace Pods
Workspace Pods ServiceAccountes are created by the DevWorkspace controller at workspace creation. This behavior can be changed now using the CheCluster field devEnvironments.serviceAccount to specify a pre-existing SA that will be used be by the DevWorkspace operator when starting the workspaces.
New DevWorkspace specification tab added to the User Dashboard
It's possible to view the specification of the DevWorkspace object that defines a workspace from the User Dashbaord Workspace details menu, in a new tab in addition to the Devfile tab.
Upgrade Kamel CLI to 1.11.0 in Universal Developer Image
Kamel CLI has been upgraded from 1.9.2 to 1.11.0.
Major Bug Fixes
Unexpeted session expiration invalidation results in random logouts
Before this fix the developer could be logged out unexpectedly because the session expired for unknown reasons.
Cannot install Eclipse Che on minikube with chectl
Before this fix it was not possible to install Che on minikube due to an error during Minikube preflight checklist
Eclipse Che 7.57.0
Major Enhancements
Updating documentation section "Calculating Che resource requirements" with CPU and VS Code based workspaces details
Use Visual Studio Code in the example in Calculating Che resource requirements and add CPU details that were missing in previous version.
Feature ported to 7.56.x
Major Bug Fixes
Che ignores changes to devfile.yaml and che-editor.yaml after pushing to a git repository (because che-server URLFetcher sometimes caches its results)
Che ignores changes to devfile.yaml and che-editor.yaml after pushing to a git repository (because che-server URLFetcher sometimes caches its results)
Fix ported to 7.56.x
VS Code shows wrong commands and files (restored from a previous workspace)
When starting a new workspace VS Code may restore the state of a previous workspace showing commands and files that do not exist in the new workspace.
Getting Started Samples are failing with 'user is not permitted use the container-build SCC'
A regression has been introduced in Eclipse Che 7.56 so that when installing Che on OpenShift using operator hub, workspaces started from Getting Started section of User Dashboard would fail to start with the error 'user is not permitted use the container-build SCC'.
Fix ported to 7.56.x
Insufficient CPU and insufficient memory errors are not caught at workspaces startup
Eclipse Che 7.56.0
Major Enhancements
VS Code is the new default IDE, Theia is deprecated
This is our first step to discontinue the support of Che-Theia as Che editor. We have been packaging VS Code and JetBrains IDEs as editors for Eclipse Che for a long time now. With these new editors we have adopted a new workspace architecture that doesn't use sidecar containers anymore. The injection of the IDE and its extensions in one "universal development container" (see diagram below) has been preferred to the use of isolated sidecars based on numerous feedbacks.
Che-Theia still uses the old workspace sidecar architecture and today we should either start packaging a sidecar-less version of Che-Theia or discontinuing it. The team that is currently maintaining Eclipse Che (primarily composed by Red Hat employees) does not have the resources to implement and maintain the sidecar-less Che-Theia.
As a consequence, unless there are volunteers ready to take this work over, Che-Theia is going to be discontinued in Che v7.60.
Allow Che administrators to enable container build capabilities for developers workspaces
An administrator can enable container builds using devEnvironments.disableContainerBuildCapabilities: true in CheCluster configuration. This allow using podman build on any workspace (adding the attribute controller.devfile.io/scc: container-build in a Devfile is not required anymore) .
Handle gracefully when an invalid devfile is found in a git repository
Workspace creation doesn't fail anymore if the developer provides an invalid Devfile (or if an invalid Devfile is found in the git repository provided by the developer). Instead a warning is shown asking wether the workspace should be started anyway with a default Devfile. This is particularly useful when a developer is editing and testing a Devfile.
Allow to specify arbitrary fields of the workspace Pod and containers using a Devfile
Using a Devfile in the git repository, a developer can override any workspace Pod and containers fields. This includes runtimeClassName, schedulerName and kubernetes extended resources such as nvidia.com/gpu.
Removed a VS Code built-in extension results in faster workspace startup
The built-in extension che-on-start has been removed as it's primary feature is not needed anymore (see this PR). The result is a faster start of VS Code in a user browser. The side effect of this change is that the terminal isn't opened at startup anymore.
Don't show the problem matcher prompt for Devfile commands in Che-Code
Every time a user runs a Devfile command in Che-Code they need to choose a problem matcher for scanning an output. This extra step is annoying and it is redundant in 99% of cases so it has been removed.
Add options for configuring DevWorkspace ServiceAccount
Support running chectl on Apple M1
Support git repositories with names containing underscores and other characters not compliant with RFC-1123
Major Bug Fixes
VS Code loading twice at workspace startup
An extension was used to open the project folder at VS Code startup. The result was VS Code beeing loaded twice in the user browser. This is not necessary anymore as we use the VS Code startup parameter --default-folder that has been (re-)introduced recently.
Gitlab repository support problems 1 and 2
Starting a workspace using a GitLab link when OAuth had been enabled, or a Personal Access Token secret had been created by the developer, failed. This has been fixed in this release.
Fix ported to 7.52.x
Image Puller doesn't work outside of openshift-operators namespace
`chectl` should not delete CheCluster namespace if it is `openshift-operator`
Eclipse Che 7.55.0
Major Enhancements
Workspace startup identifies Kubernetes quota problems
If Eclipse Che is not able to create a workspace Pod because of insufficient quota in the developer namespace, Dashboard notifies the developer, during the workspace startup, as soon as the error happens.
Allow to configure subdomain isolation for GitHub Enterprise Server in CheCluster CR
In GitHub Enterprise Server subdomains can be isolated (as it's the case for github.com) and it's now supported by Eclipse Che.
VS Code for Eclipse Che works with images that include openssl 3
VS Code fails to start on images with openssl 3 (as in registry.access.redhat.com/ubi9/ubi). It's now possible to avoid that if in the image the user installs Node.js 16 and sets the environment variable VSCODE_NODEJS_RUNTIME_DIR as described here.
Reduce steps required to trust git repositories using self-signed certificates
Configuring Eclipse Che to trust git repositories using self-signed certificates required adding the certificate twice. Some changes to Che operator allows to do that in one step now.
Major Bug Fixes
It's not possible to run a Task in Che-Code if it's not che type
Tasks included in a tasks.json file of a type other than che were not loaded in a VS Code running in a Che workspace. This has been fixed in this release and tasks.json with tasks of any type are supported and loaded in a Che workspace.
Fail to clone git repository if githost is omitted in che-git-self-signed-cert ConfigMap
When a git service uses a self-signed TLS certificate and Eclipse Che is configured to trust that certificate but the che-git-self-signed-cert doesn't include a githost section, workspaces creation failed. This has been fixed in current release.
Eclipse Che 7.54.0
Major Enhancements
Airgap support for VS Code as an Eclipse Che editor
It's now possible to run an Eclipse Che workspace using VS Code as editor in a cluster with a restricted/disconnected network (air gap). Eclipse Che is now able to run a local open-vsx registry instance within the plugin-registry pod so that VS Code editors running in workspaces can use it to manage extensions. To control what instance of open-vsx should be used in the workspaces we have introduced a new field inCheCluster CR to specify the open-vsx URL.
Avoid automatic creation of users namespaces through a configuration option
A new field in CheCluster has been added to avoid that users namespaces get created automatically. If devEnvironments.defaultNamespace.autoProvision is set to false and a user doesn't have a Che namespace, workspace creation will fail. autoProvision is set to true by default.
When starting a workspace with the same name as an existing one ask users if they wants to replace the pre-existing one
Previously, when starting a workspace with the same name of an existing one, Che would return an error and users should either manually delete the existing one or rename the new workspace. Now users are asked if they want to re-open the existing one or if they want to replace it with the new workspace.
Allow to configure git services in Che configuration
Configuring Git services OAuth will be more straightforward for administrators as it's possible to reference Git servies secrets from CheCluster CRs. On OpenShift those new configuration will be available from the OpenShift Console UI.
Faster workspace startup as a result of avoiding changes to DevWorkspace CR after it has started
The startup times of workspaces that have a persistent volume attached (the default) has been significantly improved.
Support OAuth flow for GitHub Enterprise Server
Administrators can now configure Che instances to automatically connect to GitHub Enteprise Server to retrieve and configure users personal access tokens. Note the GitHub Enterprise Cloud was already supported.
Allow to configure workspaces persistent storage from Eclipse Che CR
Workspaces persistent storage options like the strategy and the size are now configurable using CheCluster CR. It's also possible to set the storage strategy to per-workspace now so that developers will be able to run multiple workspaces concurrently.
Major Bug Fixes
Files in .vscode and .che folders of a git repository are ignored at workspace creation
Files in .vscode and .che subfolders need to be processed during workspace creation as they can contain important workspace details (as the editor and the che-theia plugins to pre-install) but were ignored in recent versions due to a regression. This has been fixed in this release.
Eclipse Che 7.53.0
Major Enhancements
Add an IDE-only workspace sample in the Dashboard getting started (without project)
A new example has been added in the Getting Started section of Eclipse Che Dashboard that allows users to start the IDE without any source code project. Git repositories can be opened from the IDE once the workspace is started.
Major Bug Fixes
Adding a container registry from Dashboard User preferences doesn't work
If a user added a container registry credential in Eclipse Che User Dashboard, that credential was not used to pull images from the registry resulting in workspaces failing to start.
Theia VS Code extensions updates
Eclipse Che 7.52.0
Major Enhancements
Allow to set environment variables into Eclipse Che core components using CheCluster
An admin can now specify arbitrary environment variables that will be applied to the containers of the core components of Eclipse Che. Those environment variables can be specified in the CheCluster Custom Resource.
Major Bug Fixes
User is not redirected to the IDE even if the workspace has started successfully
Sometimes the dashboard was not redirecting the user to the IDE.
Che Operator sometimes deploys DevWorkspace Operator even if it is present in the cluster
On OpenShift the DevWorkspace Operator is managed by OLM as a Eclipse Che dependency. As a consequence Eclipse Che Operator should not manage the DevWorkspace Operator when it's installed on OpenShift. But that was not the case and it has been fixed.
Use namespace API instead of project API to set nodeSelector and podTolerations annotations
Use namespace API instead of project API to set nodeSelector and podTolerations annotations
Eclipse Che 7.51.0
Major Enhancements
Add a VS Code extension that reports if the editor is actively used
The Che workspaces VS Code now includes an extension that tracks and report the IDE activity. That can be used by che-machine-exec to automatically stop a workspace for inactivity/run timeout.
Users can select the editor when starting an example for Che dashboard
When starting a workspace from Che samples page in user dashboard it's possible to select the editor that will be included in the development environment.
Allow admins to change workspaces inactivity and run timeout
Administrators can specify the timeout for inactivity and running workspaces with the CheCluster spec.devEnvironmentfieldssecondsOfInactivityBeforeIdlingandsecondsOfRunBeforeIdling` respectively. The default values are 30 minutes and -1 (no timeout) respectively.
Eclipse Che 7.50.0
Major Enhancements
Simplify Eclipse Che configuration format (CheCluster API v2)
CheCluster Custom Resource Definition has been updated to reflect that changes introduced with the switch to the DevWorkspaces. The result is a shorter and simpler configuration file to maintain for Eclipse Che administrators.
When a workspace is idled for inactivity user is redirected to Che dashboard
When a workspace is stopped after an inactivity now the users are redirected to the Dashboard. Previously a 503 error was displayed.
Allow an admin to specify Che default editor and containers
Che administrators can now configure the default editor (Theia, VS Code, IntelliJ or PyCharm) and the default container. Those defaults are used when the developer doesn't specify an editor or doesn't specify a devfile. The configuration can be done in the CheCluster Custom Resource in the the workspaces section using the just introduced defaultComponent and defaultEditor fields.
JetBrains IDEs running in a Che workspace autodetects the URL of a running application
As Visual Studio Code and Theia, now IntelliJ and PyCharm can detect when an application running in a Che workspace is listening to a given port and prompt the user to open the application URL. This is true even if the application has not been specified as an endpoint in the Devfile: a generic endpoint is assigned to applications that doesn't have a dedicated one.
oAuth-proxy enhancements for Azure AKS deployments
Some enhancements needed to deploy Che on Azure AKS has been contributed by @karatkep. Thank you for your contribution.
Major Bug Fixes
When using Visual Studio Code as a Che editor, the lines in the terminal are truncated and overlap
In VS Code terminal lines are not truncated anymore.
