Skip to main content

More Info:

Ensure that the scheduler.conf file has permissions of 644 or more restrictive

Risk Level

Medium

Address

Security

Compliance Standards

  • CIS Kubernetes

Triage and Remediation

Remediation

Manual Steps

  1. On every control plane node, check the current permissions of the scheduler configuration file:
  2. On every control plane node, set the file permissions to 644 as required:
  3. On every control plane node, optionally confirm the file owner and group (adjust with chown if needed according to your standard, e.g., root:root):
  4. On every control plane node, verify the fix using the audit command:
    Ensure the output shows permissions=644 (or a more restrictive value such as 640 or 600).
kubectl cannot modify file permissions on control plane nodes, so it cannot be used to fix this finding on /etc/kubernetes/scheduler.conf. The required change must be made directly on every control plane node’s filesystem; see the Manual Steps section for the exact commands to run.

Additional Reading: