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

Fix orders of yaml of policy/pod-security-policy (#14191) 

The orders of `kind` were random, and that made the doc unreadable.
This fixes the orders in consistent way in pod-security-policy.md.
pull/14193/head
Kenichi Omichi 2019-05-06 17:41:41 -07:00 committed by Kubernetes Prow Robot
parent 25ec99b46b
commit 9ae02fcbb0
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/en/docs/concepts/policy/pod-security-policy.md
View File

@ -87,8 +87,8 @@ First, a `Role` or `ClusterRole` needs to grant access to `use` the desired
policies. The rules to grant access look like this:
```yaml
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: <role name>
rules:
@ -102,8 +102,8 @@ rules:
Then the `(Cluster)Role` is bound to the authorized user(s):
```yaml
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: <binding name>
roleRef: