Release notes and known issues

OpenShift Dev Spaces runs on OpenShift 4.10–4.12 on the following CPU architectures:

For Red Hat OpenShift Dev Spaces 3.5, Red Hat will provide support for deployment, configuration, and use of the product.

The main differences between OpenShift Dev Spaces and Eclipse Che are:

Red Hat provides licensing, packaging, and support. Therefore, OpenShift Dev Spaces is considered a more stable product than the upstream Eclipse Che project.

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.

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:

For example:

spec:
  devEnvironments:
    maxNumberOfWorkspacesPerUser: 5
    maxNumberOfRunningWorkspacesPerUser: 2

spec:
  devEnvironments:
    maxNumberOfWorkspacesPerUser: 5
    maxNumberOfRunningWorkspacesPerUser: 2

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.

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.

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.

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).

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.

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.

With this update, administrators can specify the workspace startup timeout in the CheCluster Custom Resource by entering a value for spec.devEnvironments.startTimeoutSeconds.

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.

Before this update, the creation of a workspace from a public repository hosted on a GitLab server instance without configured OAuth was failing. With this update, the issue is fixed.

Before this update, there was an issue affecting devfiles with Kubernetes and OpenShift components that caused workspace creation to fail. With this update, the issue is fixed.

Before this update, workspaces failed with devfiles that had components of type Kubernetes and OpenShift due to misconfigured Subject Access Review tests by the Dev Workspace Operator. With this update, the issue has been resolved.

In OpenShift Dev Spaces 3.5, use of the Eclipse Theia editor in workspaces is deprecated. Red Hat will provide limited bug fixes and support for Eclipse Theia in OpenShift Dev Spaces during the current release lifecycle. Eclipse Theia will no longer receive enhancements for OpenShift Dev Spaces and will be removed from OpenShift Dev Spaces in the next release.

There is a known issue when updating to version 3.6: clusters that were updated to devspacesoperator.v3.5.0-0.1682130576.p require additional steps from administrators as a workaround.

Alternatively, you can use the oc command-line tool.

Currently, users are unable to create multiple workspaces from the same dashboard sample or Git repository URL after upgrading OpenShift Dev Spaces from version 3.4.

Administrators must ask users before the upgrade to push their latest workspace changes to their Git repositories and to be prepared to delete and recreate workspaces after the upgrade.

There is currently a known issue for users who are using a Kubernetes Secret with their Git-provider credentials. The user name and email for Git operations in worspaces for those users are currently taken from the user-profile Secret of the <user>-devspaces namespace.

Currently, the debugger in Microsoft Visual Studio Code - Open Source does not work in the .NET sample.

Currently, new workspaces based on a Bitbucket.org-hosted repository fail to start if the repository contains no devfile or a v1 devfile. The result is the Failed to create the workspace error message.