Chapter 4. When to use OpenShift Dev Spaces
OpenShift Dev Spaces is designed for teams that need consistent, secure, and centrally managed development environments on OpenShift. Not every team requires a cloud development platform, so evaluate your development workflow against the use cases below.
4.1. Teams that benefit from OpenShift Dev Spaces Copy linkLink copied to clipboard!
OpenShift Dev Spaces is a strong fit when your team faces one or more of these situations:
- New developers join regularly and need to be productive on day one.
- Builds fail because of differences between developer machines.
- Your organization requires credentials to stay on cluster infrastructure, not on individual machines.
- Development must happen within a controlled network boundary, including air-gapped environments.
- Projects have complex dependency chains that are difficult to reproduce consistently across developer machines.
4.2. What OpenShift Dev Spaces provides for the enterprise Copy linkLink copied to clipboard!
- On-premises control
- OpenShift Dev Spaces runs within your OpenShift cluster. When deployed on-premises, your source code and credentials stay within your own infrastructure.
- Air-gapped deployment
- OpenShift Dev Spaces operates in disconnected environments with mirrored container images and internal extension registries.
- Native OpenShift integration
- OpenShift Dev Spaces uses OpenShift RBAC, OAuth, networking, and storage directly. No additional identity or access management layer is required.
- Open devfile standard
- Workspace definitions use the devfile format, an open standard maintained by the devfile.io community.
4.3. What developers need to work with OpenShift Dev Spaces Copy linkLink copied to clipboard!
Developers need a supported web browser and network access to the OpenShift Dev Spaces dashboard URL. No local tools, CLI installations, or cluster credentials are required.