More Info:
Turn on Role Based Access Control.Risk Level
HighAddress
SecurityCompliance Standards
- CIS Kubernetes
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
-
On every control plane node, back up the existing kube-apiserver static pod manifest:
-
On every control plane node, open the manifest for editing:
Locate the
- --authorization-mode=...line underspec.containers[].command. If it does not exist, add it; if it exists, modify it so that it includesRBAC, for example:Save and exit. Editing this file will cause the kube-apiserver static pod to restart automatically. -
On every control plane node where you changed the file, confirm the kube-apiserver pod has restarted and is running:
-
On every control plane node, verify the kube-apiserver process now includes RBAC in the
--authorization-modeargument:Confirm the output shows--authorization-modewith a value that includesRBAC(for example,--authorization-mode=Node,RBAC).
Using kubectl
Using kubectl
kubectl cannot modify the kube-apiserver static pod manifest or its process flags. This finding must be remediated directly on each control plane node by editing
/etc/kubernetes/manifests/kube-apiserver.yaml; see the Manual Steps section for exact instructions.Automation
Automation

