More Info:
etcd should be configured for peer authenticationRisk Level
MediumAddress
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 (control plane) node, edit the etcd static pod manifest:
In the
spec.containers[0].command(orargs) section, add or adjust the flag so it appears exactly as:Ensure there is no other--peer-client-cert-auth=flag with a different value. -
Save the file and exit the editor. The kubelet will automatically detect the change to
/etc/kubernetes/manifests/etcd.yamland restart the etcd static pod. This causes a brief etcd/control-plane disruption; perform during a maintenance window if needed. -
On every etcd (control plane) node, wait for the etcd container to restart and become running:
(Use the appropriate container runtime command for your nodes.)
-
On every etcd (control plane) node, verify the flag is now set:
The command should return the etcd process line containing
--peer-client-cert-auth=trueand no occurrences with=false.
Using kubectl
Using kubectl
kubectl cannot modify the etcd static pod manifest or its process flags, so this finding cannot be fixed via the Kubernetes API. To remediate, you must edit
/etc/kubernetes/manifests/etcd.yaml directly on every etcd node; follow the guidance in the Manual Steps section.Automation
Automation

