Chapter 2. New features and enhancements
2.1. Support building a custom devfile registry from a Bitbucket server
With this update, admins can create a custom devfile registry from a clone of the devfile registry Git repository that is hosted on Bitbucket.
Additional resources
2.2. Users can configure Git personal access tokens in User Preferences
With this update, the User Preferences menu features a Personal Access Token tab. You can use the tab to manage GitHub, GitLab, Bitbucket, and Microsoft Azure DevOps personal access tokens. This applies to tokens created from the OpenShift Dev Spaces Dashboard UI as well as those created manually, using a Kubernetes secret.
Additional resources
2.3. Managing workspaces $HOME directory persistence
This release features two CheCluster CRs fields for managing persistences related to workspaces $HOME directory:
-
The
spec.devEnvironments.persistUserHome
field contains configuration settings related to the persistence of /home/user/ in workspaces. -
The
spec.devEnvironments.persistUserHome.enabled
determines whether /home/user/ will persist in workspaces. The persistence of these values is disabled by default.
Additional resources
2.4. Overriding OpenShift cluster-wide proxy settings with DevWorkspace operator configuration
Previously, trusted TLS certificates configured in OpenShift Dev Spaces were ignored if an OpenShift cluster-wide proxy was configured. With this update, you can configure DevWorkspace operator to avoid this undesired behavior.
Additional resources
2.5. Commands imported from a parent devfile available as Microsoft Visual Studio Code - Open Source tasks
With this update, commands defined in the parent devfile are now available in Microsoft Visual Studio Code - Open Source as tasks.
Additional resources
2.6. Simplified procedure to add a Git personal access token
Previously, users had to provide a Git username when adding a personal access token. This step was redundant and caused errors. With this update, the step is removed from the procedure.
Additional resources
2.7. Specifying the devfile component that hosts an IDE
By default, OpenShift Dev Spaces hosts the IDE (Microsoft Visual Studio - Open Source Code or JetBrains IntelliJ IDEA Community Edition) in the first container specified in a devfile. With this update, you can specify the component that will host the IDE using the attribute controller.devfile.io/merge-contribution: true
.
In the following example, the IDE will be hosted in "component2":
schemaVersion: 2.2.0 components: - name: component1 container: image: quay.io/sclorg/postgresql-15-c9s:c9s - name: component2 attributes: controller.devfile.io/merge-contribution: true container: image: quay.io/devfile/developer-base-image:latest
schemaVersion: 2.2.0
components:
- name: component1
container:
image: quay.io/sclorg/postgresql-15-c9s:c9s
- name: component2
attributes:
controller.devfile.io/merge-contribution: true
container:
image: quay.io/devfile/developer-base-image:latest
Additional resources
2.8. Automatic Podman login to the OpenShift internal registry
With this update, the TLS certificate of the OpenShift internal container registry is trusted by Podman. You can use Podman to pull images without adding the certificates manually.
Additional resources
2.9. Automatic update of existing workspace IDE after OpenShift Dev Spaces upgrade
With this update, the IDE of existing workspaces will be updated automatically after an upgrade or whenever the definition of the IDE changes.
Additional resources
2.10. Workspace loading page shows detailed startup progress
With this update, the "Waiting for a workspace to start" step on the workspace loading page features 7 subtasks. This enhancement provides better progress feedback and makes troubleshooting easier.
Additional resources
2.11. New DevWorkspace Operator metrics
With this update, the following metrics are available in the OpenShift Console Operator metrics:
- workspace CPU and memory usage
- node CPU and memory usage
- number of running workspaces
Additional resources