-
Notifications
You must be signed in to change notification settings - Fork 55
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.
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
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for vcluster-docs-site ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
9f56886 to
d3a3e9d
Compare
d3a3e9d to
d4a0b82
Compare
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
|
Claude finished @guowenatk's task in 1m 6s —— View job Review SummaryFound one grammar error that needs fixing. The change from "cluster" to "host cluster" on line 10 correctly addresses the review feedback. Issues Found:
Other Changes:
|
|
|
||
| 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 host 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The review comment by Piotr1215 is correct - "each namespace belongs to a cluster" should specify "host cluster" for clarity. This change addresses that issue.
| ::: | ||
|
|
||
| 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Grammar error: "delete namespaces that haven been idle" should be "delete namespaces that have been idle"
| - [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 | |
| - [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 have been |
Content Description
Update what-are-namespaces content
Preview Link
https://deploy-preview-1473--vcluster-docs-site.netlify.app/docs/platform/next/understand/what-are-namespaces
Internal Reference
Closes DOC-685
Note
Updates the "What Are Namespaces" documentation to clarify that namespaces belong to host clusters, adds links to creation methods and access management, and expands the feature list with key namespace capabilities.
Generated by Claude for 2ee78ff
@netlify /docs