Skip to content
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

Jump to bottom

comment version #15808

Closed
wants to merge 1 commit into from
Closed

comment version #15808

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
2 changes: 1 addition & 1 deletion content/en/docs/concepts/overview/working-with-objects/namespaces.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,7 +101,7 @@ in some namespaces. However namespace resources are not themselves in a namespa
And low-level resources, such as [nodes](/docs/admin/node) and
persistentVolumes, are not in any namespace.

To see which Kubernetes resources are and aren't in a namespace:
To see which Kubernetes resources are and aren't in a namespace, only support over v1.11.0:
Copy link
Contributor

Choose a reason for hiding this comment

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

1.11.0 is a "long" history. We are about to deprecate docs for 1.11.0. Does it still make sense to mention an old version in the new doc?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I know it, but in production env, i think 1.10.0 still exist, comment version is exact.


```shell
# In a namespace
Expand Down