Register and document RBAC autoupdate

Update content/en/docs/reference/labels-annotations-taints/_index.md

Co-authored-by: Tim Bannister <tim@scalefactory.com>
This commit is contained in:
Manish Kumar 2022-08-22 16:24:44 +05:30
parent 7ce007e43c
commit 001249edfd
1 changed files with 11 additions and 0 deletions

View File

@ -635,6 +635,17 @@ or updating objects that contain Pod templates, such as Deployments, Jobs, State
See [Enforcing Pod Security at the Namespace Level](/docs/concepts/security/pod-security-admission)
for more information.
### rbac.authorization.kubernetes.io/autoupdate
Example: `rbac.authorization.kubernetes.io/autoupdate: "false"`
Used on: ClusterRole, ClusterRoleBinding, Role, RoleBinding
When this annotation is set to `true`, default RBAC ClusterRole and ClusterRoleBinding objects are automatically updated at server start to add missing permissions and subjects (extra permissions and subjects are left in place). To prevent autoupdating a particular role or rolebinding, set this annotation to `false`.
If you create your own ClusterRole and set this annotation, `kubectl auth reconcile`
(which allows reconciling arbitrary RBAC objects in a {{< glossary_tooltip text="manifest" term_id="manifest" >}}) respects this annotation and does not automatically add missing permissions and
subjects.
### kubernetes.io/psp (deprecated) {#kubernetes-io-psp}
Example: `kubernetes.io/psp: restricted`