More Info:
Verifies that the controller manager —bind-address is set to 127.0.0.1 so its metrics and health endpoints are not exposed on the network.Risk Level
HighAddress
SecurityCompliance Standards
- CIS Kubernetes
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
- On every control plane node, back up the existing manifest so you can roll back if needed:
- Edit the controller manager static pod manifest on that control plane node:
- In the container command/args section, set or correct the bind address flag so it is exactly:
--bind-address entries with different values. Save and exit.Note: updating this static pod manifest will cause the kube-controller-manager pod to be restarted automatically by the kubelet.
- Wait for the kube-controller-manager pod to restart and become Running on that node:
- Repeat steps 1–4 on every other control plane node.
- Verify on each control plane node that the controller manager is now running with the correct bind address:
Using kubectl
Using kubectl
kubectl cannot modify the kube-controller-manager static pod manifest or its process flags. This finding must be fixed directly on each control plane node by editing
/etc/kubernetes/manifests/kube-controller-manager.yaml; see the Manual Steps section for exact host-level instructions.Automation
Automation

