kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #40557 from Zhuzhenghao/rbac 

Cleanup page rbac
pull/40568/head
Kubernetes Prow Robot 2023-04-08 06:01:14 -07:00 committed by GitHub
parent 47d961a98d c1f4c5c4a2
commit d99127dfb0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
content/en/docs/reference/access-authn-authz/rbac.md
View File

@ -929,8 +929,8 @@ to a role that grants that permission. To allow a user to create/update role bin
1. Grant them a role that allows them to create/update RoleBinding or ClusterRoleBinding objects, as desired.
2. Grant them permissions needed to bind a particular role:
* implicitly, by giving them the permissions contained in the role.
* explicitly, by giving them permission to perform the `bind` verb on the particular Role (or ClusterRole).
* implicitly, by giving them the permissions contained in the role.
* explicitly, by giving them permission to perform the `bind` verb on the particular Role (or ClusterRole).
For example, this ClusterRole and RoleBinding would allow `user-1` to grant other users the `admin`, `edit`, and `view` roles in the namespace `user-1-namespace`:
@ -1105,7 +1105,7 @@ Examples:
* Test applying a manifest file of RBAC objects, displaying changes that would be made:
```
```shell
kubectl auth reconcile -f my-rbac-rules.yaml --dry-run=client
```
@ -1260,7 +1260,7 @@ Here are two approaches for managing this transition:
Run both the RBAC and ABAC authorizers, and specify a policy file that contains
the [legacy ABAC policy](/docs/reference/access-authn-authz/abac/#policy-file-format):
```
```shell
--authorization-mode=...,RBAC,ABAC --authorization-policy-file=mypolicy.json
```