public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 12:38:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

Incorrect/self-referencing link

Browse Source
This commit is contained in:
Billy Tat
2024-09-22 10:17:26 -07:00
parent 2b36bf35c1
commit efd2bd289e
12 changed files with 13 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-2.5/how-to-guides/advanced-user-guides/manage-projects/manage-namespaces.md
+1 -2
View File
@@ -22,8 +22,7 @@ Resources that you can assign directly to namespaces include:
To manage permissions in a vanilla Kubernetes cluster, cluster admins configure role-based access policies for each namespace. With Rancher, user permissions are assigned on the project level instead, and permissions are automatically inherited by any namespace owned by the particular project.
> **Note:** If you create a namespace with `kubectl`, it may be unusable because `kubectl` doesn't require your new namespace to be scoped within a project that you have access to. If your permissions are restricted to the project level, it is better to [create a namespace through Rancher](manage-namespaces.md) to ensure that you will have permission to access the namespace.
> **Note:** If you create a namespace with `kubectl`, it may be unusable because `kubectl` doesn't require your new namespace to be scoped within a project that you have access to. If your permissions are restricted to the project level, it is better to [create a namespace through Rancher](#creating-namespaces) to ensure that you will have permission to access the namespace.
## Creating Namespaces