Skip to main content

More Info:

Ensure that the controller manager pod specification file has permissions of 644 or more restrictive.

Risk Level

High

Address

Security

Compliance Standards

  • CIS Kubernetes

Triage and Remediation

Remediation

Manual Steps

  1. On every control plane node, check the current permissions of the controller manager manifest file:
  2. If the permissions are more permissive than 644 (e.g., 664, 666, 777), restrict them:
  3. Confirm the new permissions are correctly set (this runs the same way as the audit):
kubectl cannot modify host-level file permissions for /etc/kubernetes/manifests/kube-controller-manager.yaml on control plane nodes. This fix must be applied directly on each control plane node’s filesystem; see the Manual Steps section for the required commands and procedure.

Additional Reading: