Skip to main content

More Info:

Ensure that the certificate authorities 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 worker node, identify the client CA file path used by kubelet:
  2. Review the file and confirm it is the correct client CA for your environment (to avoid changing ownership on an unintended file):
    If this is not the expected CA, stop and determine the correct CA file before proceeding.
  3. Change the file ownership to root:root (only after confirming in step 2):
  4. (Optional but recommended) Restrict permissions to read-only for root if compatible with your tooling:
  5. Verify the ownership is now root:root using the audit logic on the same worker node:
    Confirm the output is:
kubectl cannot change file ownership on worker node filesystems, including the kubelet client CA file referenced by /var/lib/kubelet/config.yaml. To fix this finding you must adjust file ownership directly on every worker node at the host level; follow the guidance in the Manual Steps section.
Usage (on every worker node, as root):

Additional Reading: