Organize workspace namespaces
Organize how OpenShift Dev Spaces creates and manages projects for workspaces so that you can enforce naming conventions, pre-provision resources, and synchronize configurations across teams.
- How workspace namespaces are organized
OpenShift Dev Spaces isolates workspaces for each user in a project, identified by labels and annotations. If the project does not exist, OpenShift Dev Spaces creates it from a template. - Set the workspace namespace naming convention
Set the project name template that OpenShift Dev Spaces uses when creating workspace projects to enforce naming conventions and organizational compliance. - Provision projects in advance
Provision workspace projects in advance, rather than relying on automatic provisioning, to control namespace naming and apply custom resource quotas. Repeat the procedure for each user. - Synchronize resources across user namespaces
SynchronizeConfigMaps,Secrets,PersistentVolumeClaims, and other Kubernetes objects from theopenshift-devspacesnamespace to user-specific namespaces to provide consistent workspace configurations. - Use Kubernetes namespaces instead of OpenShift projects
Use standard Kubernetes namespaces directly on OpenShift Container Platform instead of using the ProjectRequest API to bypass cluster-specific Project Templates.
Related concepts