Skip to main content

More Info:

Ensure that the controller-manager.conf file ownership is set to root:root.

Risk Level

Low

Address

Security

Compliance Standards

  • CIS Kubernetes

Triage and Remediation

Remediation

Manual Steps

  1. On every control plane node, confirm the file exists and view current ownership:
  2. On every control plane node, change the file owner and group to root:root:
  3. (Optional) On every control plane node, lock down permissions if needed (common setting is 600):
  4. On every control plane node, verify the ownership is now root:root:
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.
Usage:
  • Run this script on every control plane node as root, for example:

Additional Reading: