Release notes and known issues

OpenShift Dev Spaces runs on OpenShift 4.10 and 4.11 on the following CPU architectures:

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

OpenShift Dev Spaces 3.3 has been tested on Chrome version 101.0.4951.54 (Official Build) (64-bit).

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.

This enhancement adds an autoProvision field to the CheCluster custom resource where OpenShift Dev Spaces administrators can disable automatic provisioning of user namespaces:

spec:
   components
   containerRegistry
   devEnvironments:
     defaultNamespace:
       autoProvision: true 

With this update, the OpenShift Toolkit extension for Microsoft Visual Studio Code - Open Source is updated to version 1.0.0, which provides support for odo 3.3.0.

With this update, administrators can select OAuth application Secrets of their Git providers in the CheCluster Custom Resource and the OpenShift web console.

With this update, you can use Microsoft Visual Studio Code - Open Source in workspaces in a restricted environment. To manage extensions, OpenShift Dev Spaces now includes a locally cached Open VSX Registry instance in the plugin registry pod.

In OpenShift Dev Spaces 3.3, the default editor in workspaces is Microsoft Visual Studio Code - Open Source IDE.

This enhancement updates the options for the dsc server:delete CLI command:

With this update, OpenShift Dev Spaces fetches the latest versions of the devfile.yaml and che-editor.yaml files in the remote Git repository when you use the URL for that repository to start a new workspace.

In OpenShift Dev Spaces 3.3, the Universal Developer Image (UDI) is updated as follows:

In OpenShift Dev Spaces 3.3, the sample projects provided in the dashboard have changed as follows:

With this update, Calculating OpenShift Dev Spaces resource requirements has been improved to include CPU details and Microsoft Visual Studio Code - Open Source, which is the new default editor.

With this update, users can specify arbitrary fields and override any fields for the workspace Pod and containers in a devfile. This includes runtimeClassName, schedulerName, and such Kubernetes extended resources as nvidia.com/gpu. To do that, users can use the new pod-overrides and container-overrides attributes.

With this update, an Empty Workspace tile is available in the dashboard from which you can create an empty workspace. Such a workspace starts with your IDE of choice and the UDI image containing various tools and CLI applications for software development in Java, Python, Node.js, C/C++, PHP, .Net and other languages. Once opened, you can use the IDE in the workspace to clone a remote Git repository.

With this update, administrators can configure such options as storage class and size of workspaces in the CheCluster custom resource.

This enhancement makes it easier for administrators to add a Git provider’s self-signed certificate in OpenShift Dev Spaces. See the steps to do so in Git with self-signed certificates.

With this update, administrators can enable container builds by setting devEnvironments.disableContainerBuildCapabilities: true in the CheCluster custom resource. This enables users to run podman build on any workspace. Adding the attribute controller.devfile.io/scc: container-build in a devfile is no longer required.

With this update, OpenShift Dev Spaces displays a warning for users in the Creating a workspace page that the devfile in the remote Git repository is invalid. The warning offers users two options: Continue with the default devfile or Reload. This feature is particularly useful when a user is editing and testing a devfile.

With this update, OpenShift Dev Spaces supports subdomain isolation for GitHub Enterprise Server customers. Administrators can enable subdomain isolation in the CheCluster custom resource:

spec:
  gitServices:
    github:
      - endpoint: 'https://github.com'
        secretName: github-oauth-config
        disableSubdomainIsolation: true

As of OpenShift Dev Spaces 3.3, the .NET sample project has been reintroduced. It has been updated to run with .NET version 7.

Before this update, workspaces failed to start when using a devfile that points to a private container registry. This failure occurred even though the user had added the registry in the Add Container Registry dialog in the dashboard’s User Preferences. With this update, you can start workspaces from a devfile that points to a container image in a private container registry. Before starting a workspace with such a devfile, you must add the registry in the Add Container Registry dialog in the dashboard’s User Preferences.

Before this update, a regression issue caused files in the /.vscode/ and /.che/ subfolders of the cloned remote Git repository to be ignored during workspace creation. This issue was only relevant to Git repositories that are hosted on GitHub, GitLab, or Bitbucket. With this update, files in these subfolders are fetched and processed during workspace creation.

Before this update, having the CheCluster custom resource with spec.components.imagePuller.enable: true in the prod-namespace namespace resulted in Kubernetes Image Puller Operator failing due to an invalid OperatorGroup. That was causing the following error message: Operator failed OwnNamespace InstallModeType not supported, cannot configure to watch own namespace. With this update, this issue is resolved with Kubernetes Image Puller Operator creating a correct OperatorGroup with empty targetNamespaces.

Before this update, dsc server:delete --delete-namespace deleted any namespace in which the OpenShift Dev Spaces instance had been installed, even the openshift-operators namespace if inadvertently chosen during installation. Removal of the openshift-operators namespace might result in unintended removal of other installed Operators. With this update, the dsc server:delete command with the --delete-namespace option does not remove the openshift-operators namespace.

Before this update, no error message was shown a when workspace failed to start due to a Kubernetes quota. With this update, the error is successfully displayed during workspace startup when OpenShift Dev Spaces is unable to create a workspace Pod because of an insufficient quota in the user namespace.

Before this update, workspace creation failed on OpenShift Dev Spaces if an administrator had configured to trust a Git provider’s self-signed TLS certificate with a che-git-self-signed-cert ConfigMap that lacked a githost section. The resulting /etc/gitconfig file contained a malformed http directive that didn’t match any URL. With this update, this issue is resolved, and the /etc/gitconfig file contains an [http] line as expected.

Before this update, starting a workspace with a name that was in use for another workspace resulted in the Creating a workspace page showing a Failed to create a workspace error message. With this update, the Creating a workspace page warns users of an Existing workspace found and prompts users to Open the existing workspace or Create a new workspace.

In the next release, OpenShift Dev Spaces 3.4, the Eclipse Theia editor will be deprecated and its extensions will no longer be maintained. Eclipse Theia will be removed in a later release of OpenShift Dev Spaces. Red Hat will no longer provide bug fixes and support for Eclipse Theia in OpenShift Dev Spaces but will provide security fixes until its removal from OpenShift Dev Spaces. Although your users can continue to optionally use Eclipse Theia until its removal, you must prepare to migrate your users to Visual Studio Code - Open Source, which is introduced as the new default editor with air gap support in OpenShift Dev Spaces 3.3.

In OpenShift Dev Spaces 3.3, the following devfile samples have been removed:

Bug fixes and support are provided only through the end of the OpenShift Dev Spaces 3.2 lifecycle.

There is currently a known issue when starting workspaces that clone private Git repositories. After successfully cloning and reading the remote Git repository, the project-clone container fails to checkout a specified Git revision, for example a feature branch or PR branch. As a result of this error, the remote Git repository is cloned into a temporary directory named project-clone-<random_characters>.

Currently, there is a known issue with the Java Gradle sample in restricted environments. Running the 1-build command to build an application might result in the FAILURE: Build failed with an exception error and failure to load a native library or not resolving a plug-in artifact in plug-in repositories. There is currently no workaround for this issue.