Skip to main content

More Info:

If kube-proxy is running, ensure that the file ownership of its kubeconfig file is set to root:root.

Risk Level

Low

Address

Security

Compliance Standards

  • CIS GKE

Triage and Remediation

Remediation

Manual Steps

  1. On every worker node, confirm the kube-proxy kubeconfig file exists and review its current ownership:
  2. On every worker node, change the file owner and group to root:root:
  3. (Optional, only if permissions also need tightening) On every worker node, restrict permissions to owner read/write only:
  4. On every worker node, verify the ownership is now root:root:
kubectl cannot change file ownership on worker node filesystems, including /var/lib/kube-proxy/config.conf. This must be fixed directly on every worker node via host-level commands; follow the Manual Steps section to update ownership and verify.

Additional Reading: