What Are Namespaces
Namespaces managed through projects, also known as spaces, are deprecated in v5.0.0. Platform management of namespaces is planned for removal in a later v5.0 patch release. Existing Kubernetes namespaces and their workloads will remain on their clusters after removal. The platform will no longer manage them.
Until then, platform-managed namespaces keep working in projects outside tenants. Tenant projects can't create or import them, and they can't be moved into a tenant project. Move workloads that need continued platform management to clusters.
Namespaces are regular Kubernetes namespaces managed by vCluster Platform that are owned by a user or team. In Kubernetes, namespaces provide a mechanism for isolating groups of resources within a single cluster.
In vCluster Platform, each namespace belongs to a Control Plane Cluster and project. Namespaces can be created from a template to enforce isolation best practices or created manually by project admins. Admins can manage access and users can connect via CLI.
For applications that require multiple namespaces or need to create cluster scoped resources, clusters are recommended instead.
There are multiple key features you can use with namespaces:
- Auto Sleep & Auto Delete that puts namespaces to sleep when nobody is using them or delete namespaces that have been idle for a while.
- Isolation that applies ResourceQuotas, LimitRanges, and NetworkPolicies to a Namespace.
- Prevent Deletion that prevents a Namespace from deletion.
- Custom Links that adds custom links to namespaces that point to external resources such as GitHub pull requests, Jira issues, or documentation.