Skip to main content

More Info:

If the kube-proxy kubeconfig file exists it should be owned by root:root so only privileged users can read or modify it. Incorrect ownership risks exposure of connection settings.

Risk Level

Medium

Address

Security

Compliance Standards

  • CIS Kubernetes

Triage and Remediation

Remediation

Manual Steps

  1. On every worker node, check if the proxy kubeconfig file exists and view its current ownership:
  2. If the file exists and is not owned by root:root, change its ownership on that worker node:
  3. Confirm the permissions are appropriate (readable only by root or as per your policy) and adjust if needed, for example:
  4. Repeat steps 1–3 on every worker node in the cluster where /etc/kubernetes/proxy.conf is present.
  5. Verify on each worker node that the ownership is now correctly set to root:root:
This setting is controlled by file ownership on each worker node’s filesystem and cannot be changed through the Kubernetes API, so kubectl cannot remediate it. To fix the issue, adjust the ownership of /etc/kubernetes/proxy.conf directly on every worker node as described in the Manual Steps section.