More Info:
Do not use automatically generated self-signed certificates for TLS connections between peers.Risk Level
LowAddress
SecurityCompliance Standards
- CIS Kubernetes
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
- On every etcd (control plane) node, back up the current etcd static pod manifest:
- Open the etcd manifest for editing:
- In the
commandorargslist for the etcd container, locate any--peer-auto-tlsentry and either delete that line or set it explicitly to false, for example:
--peer-auto-tls=true in the file. Save and exit the editor.Note: editing this file will cause the kubelet to restart the etcd static pod.
- Wait for the etcd pod to be recreated and confirm it is running (on the control plane node):
- On the same node, verify the running etcd process no longer has
--peer-auto-tls=trueand, if present, is set to false:
- Inspect the command line shown and confirm that:
- there is no
--peer-auto-tls=true, and - if
--peer-auto-tlsappears, it is--peer-auto-tls=false.
Using kubectl
Using kubectl
kubectl cannot modify the etcd static pod manifest or its process flags. To remediate this finding, you must edit
/etc/kubernetes/manifests/etcd.yaml directly on every etcd (control plane) node; follow the guidance in the Manual Steps section for the exact host-level changes.Automation
Automation

