This documentation is for a release that is no longer maintained
See documentation for the latest supported version.Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
Chapter 2. New features and enhancements
2.1. Configuring remotes using a factory URL Link kopierenLink in die Zwischenablage kopiert!
With this update, you can configure the Git remotes of a new workspace created by using the factory URL. The remotes query parameter can be set to a comma-separated list of Git remotes, with an optional name for each.
Additional resources
2.2. Limiting the number of workspaces per user Link kopierenLink in die Zwischenablage kopiert!
With this update, administrators can set a limit on the total number of workspaces, and running workspaces per user by using the following parameters in the CheCluster Custom Resource:
-
spec.devEnvironments.maxNumberOfWorkspacesPerUser -
spec.devEnvironments.maxNumberOfRunningWorkspacesPerUser
For example:
spec:
devEnvironments:
maxNumberOfWorkspacesPerUser: 5
maxNumberOfRunningWorkspacesPerUser: 2
spec:
devEnvironments:
maxNumberOfWorkspacesPerUser: 5
maxNumberOfRunningWorkspacesPerUser: 2
Additional resources
2.3. Git Services tab in the dashboard User Preferences page Link kopierenLink in die Zwischenablage kopiert!
With this update, a Git Services tab is added to the User Preferences page in the dashboard. This tab lists the Git providers that you as a user have granted access to. Supported Git providers are GitHub (github.com and Enterprise), GitLab (SaaS and Server), Bitbucket (Cloud and Server), and Microsoft Azure Repos.
You can revoke access for GitHub through the menu in the Git Services tab. This feature isn’t available for other Git providers.
Additional resources
2.4. Installation of pre-release versions of OpenShift Dev Spaces Link kopierenLink in die Zwischenablage kopiert!
With this update, administrators can run dsc server:deploy --olm-channel=… to install unreleased and unsupported versions of OpenShift Dev Spaces from the release candidate (latest) channel or the CI build (next) channel.
Additional resources
2.5. GUI improvement in the default IDE for when a workspace stops Link kopierenLink in die Zwischenablage kopiert!
This enhancement improves the GUI of the OpenShift Dev Spaces build of Microsoft Visual Studio Code - Open Source for stopped workspaces. A new dialog notifies the user that the workspace has stopped and displays the cause. The dialog offers the user two buttons: return to the dashboard or restart the workspace.
Additional resources
2.6. Support for Microsoft Azure Repos of Microsoft Azure DevOps Services Link kopierenLink in die Zwischenablage kopiert!
With this update, users can start workspaces from public and private Git repositories hosted on Microsoft Azure Repos. Git repository maintainers can include devfiles in Git repositories that are hosted on Microsoft Azure Repos. Administrators can configure OAuth 2.0 for Microsoft Azure DevOps Services. Where OAuth configuration by an administrator is not permitted, users can use Microsoft Azure DevOps Services tokens as a workaround. This update adds Microsoft Azure Repos to the range of Git providers that OpenShift Dev Spaces already supports, including GitHub (github.com and Enterprise), GitLab (SaaS and Server), and Bitbucket (Cloud and Server).
Additional resources
2.7. Selecting the ephemeral storage strategy in CheCluster Link kopierenLink in die Zwischenablage kopiert!
With this update, administrators can set devEnvironments.storage.pvcStrategy: ephemeral in the CheCluster Custom Resource as the default storage strategy for new workspaces of all users. This setting does not affect users' existing workspaces.
Users can select the ephemeral storage strategy per workspace through the storage-type setting in the dashboard.
Additional resources
2.8. Dev Workspace Operator accepts devfile volume sizes for per-workspace storage strategy Link kopierenLink in die Zwischenablage kopiert!
With this update, Dev Workspace Operator accepts the volume size specified in the devfile volume when the persistent volume (PV) is created per-workspace. The PV size is determined by summing the size of all devfile volumes. When the PV is created per-user, the volume size is ignored.
Additional resources
2.9. Specifying workspace startup timeout Link kopierenLink in die Zwischenablage kopiert!
With this update, administrators can specify the workspace startup timeout in the CheCluster Custom Resource by entering a value for spec.devEnvironments.startTimeoutSeconds.
Additional resources
2.10. Changing workspace pod scheduler in the CheCluster Custom Resource Link kopierenLink in die Zwischenablage kopiert!
With this update, administrators can replace the default OpenShift scheduler of a workspace pod with an alternative scheduler by configuring the spec.devEnvironments.podSchedulerName value in the CheCluster Custom Resource. The alternative scheduler is applied to all newly started workspaces.
Additional resources