Major Enhancements
Exposed URL parameters on the 'Git Repo Options' panel on the User Dashboard
Git branch, remotes, and path to devfile URL parameters are now exposed on the 'Git Repo Options' panel of the User Dashboard:
Support raw devfile URLs without yaml
extension
Starting from this release, you can create workspaces from any URL that serves a valid devfile, such as in the following cases:
- https://registry.devfile.io/devfiles/ollama/1.0.0
- https://registry.devfile.io/devfiles/dotnet60/1.0.3
Add initContainer for initializing persistentHome when $HOME persistence is enabled
With this release, if you have $HOME persistence enabled, there is an initContainer
that runs the entrypoint
script and initializes persistentHome. This prevents a race condition from occurring.
Previously, the persistent user home setup occurred in the entrypoint of the tooling container. Notably, the entrypoint
was used to run stow
to make symbolic links for the home directory to be saved on the PVC. If a postStart event depends on files or edits files located in the home directory, there is a risk of a race condition caused by the post-start event running before the stow
execution is finished. To prevent this, the entrypoint
script must be completed before the postStart events run.
You can find more details about this enhancement in the demo video.
Major Bug fixes
Extension secrets are lost on workspace restart
Extension secrets for Visual Studio Code - Open Source ("Code - OSS") are no longer lost after workspace restart, but encrypted and persisted in the browser's local storage.
This allows extensions like Ansible that use Visual Studio Code Secrets Storage API to persist the data between workspace restarts in the same browser.
TODO: @vitaliy-guliy @azatsarynnyy @RomanNikitenko
merge che-incubator/che-code#340
resolve https://issues.redhat.com/browse/CRW-5942
close #22837
Projects are not cloned after restarting the workspace using the 'Restart Workspace from Local Devfile' command
Before this release, extra projects added to the devfile from a workspace were not cloned if you restarted the workspace with the 'Restart Workspace from Local Devfile' command. With this release, the issue is fixed.
The dashboard pod frequently restarts with exitCode: 137
Previously, the dashboard pod might have been frequently restarting with exitCode: 137
due to a memory leak which has been fixed in this release.
Unable to resolve parent devfile when using self-signed certs in disconnected clusters
Previously, when you used self-signed certificates on an air-gapped cluster, starting a workspace that referenced a parent devfile by URI would fail with x509: certificate signed by unknown authority
error. The defect has been fixed in this release and you can now reference a parent devfile in disconnected clusters.
TODO: @vinokurig @AObuchow merge - devfile/devworkspace-operator#1259
close - devfile/devworkspace-operator#1248
resolve - https://issues.redhat.com/browse/CRW-6001
OAuthSecret stored in plain text
Before this release, when deployed on Kubernetes, oAuthClientSecret
was stored in plain text in the CheCluster resource. That was not convenient for the GitOps approach where the cluster state is stored in Git and managed by ArgoCD. Starting from this release, you can configure the values for oAuthClientSecret
by using ExternalSecrets to keep all sensitive data out of the code base.
The workspace status changed unexpectedly to 'Starting'
Previously during a workspace startup, the status could have unexpectedly changed to 'Starting':
The defect has been fixed in this release, and status changes (except 'Failed' and 'Terminating') are ignored during workspace startup.
Start workspace page showed warning message 'Status changed unexpectedly to 'Stopped' even though workspace started successfully
Previously, during a workspace startup, the status could have been unexpectedly changed to 'Stopped' even though the workspace started successfully:
The defect has been fixed in this release, and the status changes (except 'Failed' and 'Terminating') are ignored during workspace startup.
Workspace action menu remains open
Before this release, the action menu items such as 'Open' and 'Stop Workspace' remained open on the User Dashboard after you clicked them. With this release, the issue is fixed.
Error when starting a workspace with df
and override.devfileFilename
URL parameters from the dashboard
The defect related to the errors during a workspace startup with df
, override.devfileFilename
parameters has been fixed in this release:
PROJECTS_ROOT environment variable being set incorrectly at workspace startup
Previously, PROJECTS_ROOT environment variable was set incorrectly to /projects/projects
after workspace startup. The defect has been fixed in this release and the environment variable correctly points to the /projects
directory.
Screen.Recording.2024-04-25.at.16.30.11.mov
Tooling container $PATH is overridden
Before this release, process.env.PATH
was overridden by userShellEnv.PATH
environment variable.
With this release, the values of the process.env.PATH
and userShellEnv.PATH
environment variables are merged.