More Info:
The —peer-auto-tls argument must not be set to true, as it makes etcd use automatically generated self-signed certificates for peer connections. This bypasses proper certificate authentication between etcd nodes.Risk Level
CriticalAddress
SecurityCompliance Standards
- CIS Kubernetes
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
- On every etcd (control plane) node, back up the existing manifest:
- On every etcd node, open the manifest for editing:
- In the
spec.containers[].command(orargs) section for theetcdcontainer, locate any--peer-auto-tlsentry. Either delete that argument line entirely or change it to:
-
Be aware: editing
/etc/kubernetes/manifests/etcd.yamlcauses the kubelet to restart the etcd static pod on that node. Allow a few moments for the etcd container to restart and stabilize. -
On every etcd node, verify etcd was restarted and that
--peer-auto-tlsis not set to true:
- there is no
--peer-auto-tls=truein the process arguments, and - if
--peer-auto-tlsappears, it is--peer-auto-tls=false(or the flag is absent).
Using kubectl
Using kubectl
kubectl cannot modify the etcd static pod manifest or its process flags. This finding must be fixed by editing
/etc/kubernetes/manifests/etcd.yaml directly on every etcd (control plane) node; see the Manual Steps section for the exact host-level changes and verification.Automation
Automation

