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

Prevent merge conflicts when merging master to staging

Browse Source
This commit is contained in:
Catherine Luse
2021-02-01 13:43:52 -07:00
parent 1954bbf87d 0a0590df5c
commit 4f42c7cbde
119 changed files with 417 additions and 370 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/project-admin/namespaces/_index.md
+1 -1
View File
@@ -20,7 +20,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]({{<baseurl>}}/rancher/v2.x/en/project-admin/namespaces/#creating-namespaces) 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]({{<baseurl>}}/rancher/v2.x/en/project-admin/namespaces) to ensure that you will have permission to access the namespace.
### Creating Namespaces