Skip to main content

More Info:

If the kube-proxy kubeconfig file exists it may contain connection credentials and should be protected. Permissions of 600 or more restrictive keep it readable only by root.

Risk Level

Medium

Address

Security

Compliance Standards

  • CIS Kubernetes

Triage and Remediation

Remediation

Manual Steps

  1. On each worker node, check if the kube-proxy kubeconfig file exists and view its current permissions:
  2. On each worker node where /etc/kubernetes/proxy.conf exists, set its permissions to 600:
  3. On each worker node, confirm the file is owned by root and in the root group (adjust if necessary):
  4. On each worker node, verify the final permissions match the benchmark requirement:
    The output must show:
kubectl cannot modify file permissions on worker node files such as /etc/kubernetes/proxy.conf; this must be fixed directly on each worker node’s host filesystem. Use SSH and follow the steps in the Manual Steps section to set the correct permissions.