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.
This commit is contained in:
committed by
Kubernetes Prow Robot
parent
25ec99b46b
commit
9ae02fcbb0
@@ -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:
|
policies. The rules to grant access look like this:
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
kind: ClusterRole
|
|
||||||
apiVersion: rbac.authorization.k8s.io/v1
|
apiVersion: rbac.authorization.k8s.io/v1
|
||||||
|
kind: ClusterRole
|
||||||
metadata:
|
metadata:
|
||||||
name: <role name>
|
name: <role name>
|
||||||
rules:
|
rules:
|
||||||
@@ -102,8 +102,8 @@ rules:
|
|||||||
Then the `(Cluster)Role` is bound to the authorized user(s):
|
Then the `(Cluster)Role` is bound to the authorized user(s):
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
kind: ClusterRoleBinding
|
|
||||||
apiVersion: rbac.authorization.k8s.io/v1
|
apiVersion: rbac.authorization.k8s.io/v1
|
||||||
|
kind: ClusterRoleBinding
|
||||||
metadata:
|
metadata:
|
||||||
name: <binding name>
|
name: <binding name>
|
||||||
roleRef:
|
roleRef:
|
||||||
|
|||||||
Reference in New Issue
Block a user