More Info:
If kube-proxy is running, ensure that the file ownership of its kubeconfig file is set to root:root.Risk Level
LowAddress
SecurityCompliance Standards
- CIS Kubernetes
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
-
On every worker node, confirm the kube-proxy kubeconfig file path (your affected file is
/var/lib/kube-proxy/config.conf): -
On every worker node, set the file owner and group to
root:root: -
(Optional, but recommended) On every worker node, restrict permissions so only root can read/write:
-
On every worker node, verify the ownership is now
root:root:The command must output:
Using kubectl
Using kubectl
kubectl cannot modify file ownership on worker node filesystems, including
/var/lib/kube-proxy/config.conf, so this finding cannot be fixed via the Kubernetes API. Perform the correction directly on each worker node’s host OS as described in the Manual Steps section.Automation
Automation

