Skip to main content

More Info:

Verifies that the kube-scheduler pod manifest file is owned by root:root so only privileged users can modify it.

Risk Level

Medium

Address

Security

Compliance Standards

  • CIS Kubernetes

Triage and Remediation

Remediation

Manual Steps

  1. On every control plane node, check the current ownership of the kube-scheduler manifest:
  2. Still on the control plane node, set the file owner and group to root:root:
  3. (Optional) Tighten permissions if needed so only root can modify the file:
  4. Verify the ownership is now root:root on the control plane node:
kubectl cannot change file ownership on control plane nodes, so it cannot be used to fix /etc/kubernetes/manifests/kube-scheduler.yaml. This must be corrected directly on each control plane node’s filesystem; see the Manual Steps section for how to do that.