More Info:
Do not use self-signed certificates for TLS.Risk Level
HighAddress
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
/etc/kubernetes/manifests/etcd.yamlfor editing: -
In the container
command/argslist for etcd, locate any--auto-tlsflag and either:- remove the entire
--auto-tls=...entry, or - change it explicitly to false, for example:
- remove the entire
- Save the file and exit the editor. The kubelet will automatically restart the etcd static pod when it detects the manifest change (this temporarily restarts etcd on this node).
-
After 30–60 seconds, verify on the same node that etcd is running without
--auto-tls=true: -
Inspect the output and confirm there is no
--auto-tls=trueargument present in the etcd process command line (and, if present, it is--auto-tls=falseor absent entirely). Repeat these steps on every etcd node.
Using kubectl
Using kubectl
kubectl cannot change the etcd process flags or the static pod manifest at
/etc/kubernetes/manifests/etcd.yaml on the control plane node. To remediate this finding, you must edit that file directly on every etcd node; see the Manual Steps section.Automation
Automation

