Skip to main content

More Info:

Ensure that the scheduler pod specification file ownership is set to root:root

Risk Level

Medium

Address

Security

Compliance Standards

  • CIS Kubernetes

Triage and Remediation

Remediation

Manual Steps

  1. On every control plane node, check current ownership of the scheduler manifest:
  2. On every control plane node, set the file owner and group to root:
  3. (Optional) Confirm file permissions are at least not more permissive than needed (no change required for this control, but you may review):
  4. Verify the fix on every control plane node using the audit command:
    The output must be:
kubectl cannot modify ownership of host-level files such as /etc/kubernetes/manifests/kube-scheduler.yaml on control plane nodes. This must be fixed directly on each control plane node’s filesystem; see the Manual Steps section for the exact commands to run over SSH.
Run this script on every control plane node with sufficient privileges, for example:

Additional Reading: