Skip to main content

More Info:

Do not use automatically generated self-signed certificates for TLS connections between peers.

Risk Level

Low

Address

Security

Compliance Standards

  • CIS Kubernetes

Triage and Remediation

Remediation

Manual Steps

  1. On every etcd (control plane) node, back up the current etcd static pod manifest:
  1. Open the etcd manifest for editing:
  1. In the command or args list for the etcd container, locate any --peer-auto-tls entry and either delete that line or set it explicitly to false, for example:
Ensure there is no remaining --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.
  1. Wait for the etcd pod to be recreated and confirm it is running (on the control plane node):
  1. On the same node, verify the running etcd process no longer has --peer-auto-tls=true and, if present, is set to false:
  1. Inspect the command line shown and confirm that:
  • there is no --peer-auto-tls=true, and
  • if --peer-auto-tls appears, it is --peer-auto-tls=false.
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.

Additional Reading: