More Info:
Ensure that the controller-manager.conf file ownership is set to root:root.Risk Level
LowAddress
SecurityCompliance Standards
- CIS Kubernetes
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
-
On every control plane node, confirm the file exists and view current ownership:
-
On every control plane node, change the file owner and group to root:root:
-
(Optional) On every control plane node, lock down permissions if needed (common setting is 600):
-
On every control plane node, verify the ownership is now root:root:
Using kubectl
Using kubectl
kubectl cannot modify file ownership on control plane nodes, so it cannot be used to fix
/etc/kubernetes/controller-manager.conf. This must be corrected directly on every control plane node’s host filesystem; see the Manual Steps section for the exact commands to run.Automation
Automation
- Run this script on every control plane node as root, for example:

