Skip to main content

More Info:

The kubelet configuration file should have permissions of 644 or more restrictive so that only authorized users can read or modify it. Overly permissive permissions could allow unauthorized modification of kubelet behavior.

Risk Level

Medium

Address

Security

Compliance Standards

  • CIS GKE

Triage and Remediation

Remediation

Manual Steps

  1. On every worker node, check the current permissions of the kubelet configuration file:
  2. On every worker node, set the kubelet configuration file permissions to 644:
  3. On every worker node, ensure the file owner is root (adjust if needed for your environment):
  4. On every worker node, verify the permissions are now correctly set (adapted from the audit command):
    Confirm the output is:
kubectl cannot modify file permissions on worker nodes, so it cannot be used to fix this finding on /home/kubernetes/kubelet-config.yaml. To remediate, you must change the permissions directly on every worker node’s filesystem; see the Manual Steps section for the exact commands to run over SSH.