From 9ae02fcbb0e4a966cd94a1daa9669ec7f7f6557f Mon Sep 17 00:00:00 2001 From: Kenichi Omichi Date: Mon, 6 May 2019 17:41:41 -0700 Subject: [PATCH] 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. --- content/en/docs/concepts/policy/pod-security-policy.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/policy/pod-security-policy.md b/content/en/docs/concepts/policy/pod-security-policy.md index 977a1b6a19..bbbad6eceb 100644 --- a/content/en/docs/concepts/policy/pod-security-policy.md +++ b/content/en/docs/concepts/policy/pod-security-policy.md @@ -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: 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: roleRef: