Chapter 2. New features and enhancements

You can now connect to multiple Dev Spaces workspaces simultaneously by using the JetBrains Gateway plugin. Previously, the plugin restricted you to a single active connection. This limitation is now removed.

Dev Spaces now supports running nested containers, which allows you to use commands like podman run directly in a workspace without kubedock. To enable this feature, set spec.devEnvironments.disableContainerRunCapabilities to false in the CheCluster custom resource.

Known issue

On OpenShift Container Platform 4.20.3, an SELinux regression prevents nested containers from functioning on clusters that were upgraded from version 4.17. This issue is specific to long-running, upgraded clusters and does not affect new clusters installed with OpenShift Container Platform 4.19 or 4.20.

For more information, see the documentation and the OpenShift Container Platform 4.20 release notes.

You can now specify a name for a workspace when you create it from the Getting Started page on the User Dashboard.

You can now rename an existing workspace by adding the kubernetes.io/metadata.name label to the DevWorkspace custom resource.

This release changes the default behavior for Persistent Volume Claims (PVCs) that are synchronized to user namespaces. Previously, deleting the source PVC would also delete the synchronized PVCs in each user namespace.

To prevent accidental data loss, synchronized PVCs are no longer deleted by default when the source PVC is removed. This behavior applies to PVCs configured by following the procedure in the Configuring a user namespace documentation.

Previously, when you attempted to add a personal access token (PAT) for a Bitbucket Server from the User Preferences > Personal Access Tokens page, no clear error was shown if the server’s TLS certificate was not imported into Dev Spaces.

Now, if the certificate is missing or untrusted, the User Dashboard displays the following error message: The required SSL certificate is missing or not trusted by the system. Please contact your administrator.

The che-code editor, which is based on Visual Studio Code - Open Source (Code - OSS), is now updated to version 1.103.2.

You can read about the new features and fixes from the upstream project in the VS Code release notes.

If the CheCluster controller fails to reconcile, the devspaces-operator pod now provides more detailed error logs to aid in troubleshooting.

You can now connect to a DevWorkspace by using the SSH protocol from your local VS Code-based editor.