More Info:
Configure TLS encryption for the etcd service.Risk Level
MediumAddress
SecurityCompliance Standards
- CIS Kubernetes
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
- On every etcd (control plane) node, back up the current manifest and identify the existing TLS files:
- If you do not already have an etcd server certificate and key, generate them (example using existing etcd CA under /etc/kubernetes/pki/etcd):
- Edit the etcd static pod manifest on each etcd node to configure
--cert-fileand--key-file(this edit will automatically restart the etcd pod when saved):
- Confirm the referenced files exist and are readable by the kubelet/container runtime:
- Wait 30–60 seconds for the static pod to be recreated, then confirm the etcd pod is running (from any machine with kubectl access):
- Verification on every etcd node: ensure the etcd process is running with the desired
--cert-fileand--key-filearguments:
Using kubectl
Using kubectl
kubectl cannot modify host-level static pod manifests or etcd 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 how to update the manifest and verify the etcd --cert-file and --key-file arguments.Automation
Automation

