whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

rbac: make it clear that subjects are case sensitive (#8007)

Browse Source
This commit is contained in:
Eric Chiang
2018-04-06 12:12:08 -07:00
committed by k8s-ci-robot
parent b0b269b4d8
commit 45a0819cdc
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/admin/authorization/rbac.md
+4 -4
View File
@@ -88,7 +88,7 @@ metadata:
namespace: default
subjects:
- kind: User
name: jane
name: jane # Name is case sensitive
apiGroup: rbac.authorization.k8s.io
roleRef:
kind: Role
@@ -102,7 +102,7 @@ This allows administrators to define a set of common roles for the entire cluste
then reuse them within multiple namespaces.
For instance, even though the following `RoleBinding` refers to a `ClusterRole`,
"dave" (the subject) will only be able to read secrets in the "development"
"dave" (the subject, case sensitive) will only be able to read secrets in the "development"
namespace (the namespace of the `RoleBinding`).
```yaml
@@ -114,7 +114,7 @@ metadata:
namespace: development # This only grants permissions within the "development" namespace.
subjects:
- kind: User
name: dave
name: dave # Name is case sensitive
apiGroup: rbac.authorization.k8s.io
roleRef:
kind: ClusterRole
@@ -134,7 +134,7 @@ metadata:
name: read-secrets-global
subjects:
- kind: Group
name: manager
name: manager # Name is case sensitive
apiGroup: rbac.authorization.k8s.io
roleRef:
kind: ClusterRole