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

Fix yaml sample order of configure-pod-container/ (#14259)

Browse Source 
The orders of data was random, and that made the doc unreadable.
This fixes the orders in consistent way under configure-pod-container/
This commit is contained in:
Kenichi Omichi
2019-05-10 03:01:58 -07:00
committed by Kubernetes Prow Robot
parent 5c59214ac6
commit d378484400
4 changed files with 33 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/configure-pod-container/configure-gmsa.md
+2 -2
View File
@@ -102,8 +102,8 @@ A cluster role needs to be defined for each GMSA credential spec resource. This
```
#Create the Role to read the credspec
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: webapp1-role
rules:
@@ -117,8 +117,8 @@ rules:
A service account (that pods will be configured with) needs to be bound to the cluster role create above. This authorizes the service account to "use" the desired GMSA credential spec resource. The following shows the default service account being bound to a cluster role `webapp1-role` to use `gmsa-WebApp1` credential spec resource created above.
```
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: allow-default-svc-account-read-on-gmsa-WebApp1
namespace: default