Skip to content

fix (platform): update namespaces intro #1473

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
guowenatk wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix (platform): update namespaces intro #1473

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 10 additions & 2 deletions platform/understand/what-are-namespaces.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,17 @@ sidebar_position: 7
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 cluster and project. Each namespace also was created from a template to ensure the Kubernetes namespace and objects within it conform to isolation best practices.
You can easily manage who has access to a namespace and connect to it via kubectl.
In vCluster Platform, each namespace belongs to a cluster and project. A Namespace can be [created from a template](../../next/use-platform/namespaces/create/create-with-template) to ensure the Kubernetes namespace and objects within it conform to isolation best practices
Copy link
Contributor

@Piotr1215 Piotr1215 Dec 9, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

each namespace belongs to a cluster <- this should specify what cluster (host/virtual)

or [created manually in vCluster Platform UI](../../next/use-platform/namespaces/create/create-no-template) for project admins.
Admins can also easily [manage access to a Namespace](../../next/administer/users-permissions/permissions/namespace) and users can [connect to the Namespace via CLI](../../next/use-platform/namespaces/retrieve-kube-config).

:::info
For applications that require multiple namespaces or need to create cluster scoped resources, [virtual clusters](what-are-virtual-clusters.mdx) are recommended instead.
:::

There are multiple key features you can use with namespaces:
- [Sleep Mode & Auto Delete](../../use-platform/namespaces/key-features/sleep-mode) that puts namespaces to sleep when nobody is using them or delete namespaces that haven been
idle for a while.
- [Isolation](../../use-platform/namespaces/key-features/isolation) that applies ResourceQuotas, LimitRanges, and NetworkPolicies to a Namespace.
- [Prevent Deletion](../../use-platform/namespaces/key-features/prevent-deletion) that prevents a Namespace from deletion.
- [Custom Links](../../use-platform/namespaces/key-features/custom-links) that adds custom links to namespaces that point to external resources such as GitHub pull requests, Jira issues, or documentation.