Update kustomization.md
fix typo Signed-off-by: Gaál George <gb12335@gmail.com>
This commit is contained in:
parent
1e84289623
commit
2b32f0f7a3
|
|
@ -526,7 +526,7 @@ For example, a service mesh proxy injector should be running before deploying ap
|
|||
## Role-based access control
|
||||
|
||||
By default, a Kustomization apply runs under the cluster admin account and can create, modify, delete
|
||||
cluster level objects (namespaces, CRDs, etc) and namespeced objects (deployments, ingresses, etc).
|
||||
cluster level objects (namespaces, CRDs, etc) and namespaced objects (deployments, ingresses, etc).
|
||||
For certain Kustomizations a cluster admin may wish to control what types of Kubernetes objects can
|
||||
be reconciled and under which namespaces.
|
||||
To restrict a Kustomization, one can assign a service account under which the reconciliation is performed.
|
||||
|
|
|
|||
Loading…
Reference in New Issue