More Info:
Ensure that the controller manager pod specification file ownership is set to root:root.Risk Level
MediumAddress
SecurityCompliance Standards
- CIS Kubernetes
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
-
On every control plane node, confirm the controller manager manifest exists and check its current ownership:
-
On every control plane node, set the file owner and group to root:
-
(Optional) On every control plane node, ensure any configuration management or bootstrap scripts (if present) also set the correct ownership so it is not reverted. For example, inspect for references:
-
Be aware that editing files under
/etc/kubernetes/manifestscan trigger a restart of the corresponding static pod, but changing ownership only should not modify the pod content. Proceed during a maintenance window if your change process requires it. -
On every control plane node, verify the ownership is now
root:root:The output must be:
Using kubectl
Using kubectl
Kubectl cannot modify host-level file ownership for
/etc/kubernetes/manifests/kube-controller-manager.yaml; this must be corrected directly on every control plane node via OS tools (for example, chown). See the Manual Steps section for the exact commands to run on the nodes.Automation
Automation

