Frequently asked questions

The following are common questions about Red Hat OpenShift Dev Spaces.

Is it possible to deploy applications from OpenShift Dev Spaces to an OpenShift cluster?
The OpenShift user token is automatically injected into workspace containers, which makes it possible to run oc commands against the OpenShift cluster.
For best performance, what is the recommended storage to use for Persistent Volumes used with OpenShift Dev Spaces?
Use block storage.
Is it possible to deploy more than one OpenShift Dev Spaces instance on the same cluster?
Only one OpenShift Dev Spaces instance can be deployed per cluster.
Is it possible to install OpenShift Dev Spaces offline (that is, disconnected from the internet)?
See Installing Red Hat OpenShift Dev Spaces in restricted environments on OpenShift.
Is it possible to use non-default certificates with OpenShift Dev Spaces?
You can use self-signed or public certificates. See Importing untrusted TLS certificates.
Is it possible to run multiple workspaces simultaneously?
See Enabling users to run multiple workspaces simultaneously.
Is it possible to configure OpenShift Dev Spaces to use open-vsx.org?

Yes, but this is not the default configuration. While you can connect to the public Open VSX Registry, consider these factors:

  • Service limits: API usage is organized into defined tiers. The Eclipse Foundation implements these limits to protect infrastructure from high-frequency automated traffic and to provide consistent service quality for all users. For more information, see Rate Limits and Usage Tiers and the open-vsx.org wiki.
  • Security and stability: The public registry does not have an official service-level agreement (SLA) and poses potential security risks from unvetted extensions.

    For a secure, stable, and high-performance environment, use a self-hosted registry with a curated set of extensions that meet your organization’s requirements.