More Info:
Enable kubelet client certificate rotation.Risk Level
LowAddress
SecurityCompliance Standards
- CIS Kubernetes
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
-
On every worker node, open the kubelet config file and ensure
rotateCertificatesis not set tofalse(set it totrueor remove the key). For example, usingvi:In thekubeletConfigurationsection, either remove any existingrotateCertificatesline or set it explicitly: -
Still on every worker node, check if kubelet is started with an explicit
--rotate-certificates=falseflag in its systemd drop-in: -
If the flag is present and set to
false, edit the systemd configuration and remove the--rotate-certificates=falseargument completely:In theEnvironment=orKUBELET_CERTIFICATE_ARGSline, delete--rotate-certificates=false(do not replace it withtrue; absence uses the default secure behavior). -
On every worker node, reload systemd configuration and restart the kubelet for changes to take effect (this will temporarily disrupt workloads on that node):
-
Verify on every worker node that kubelet is no longer running with
--rotate-certificates=false:Inspect the command line in the output and confirm there is no--rotate-certificates=falseflag.
Using kubectl
Using kubectl
kubectl cannot modify kubelet host-level configuration such as
/var/lib/kubelet/config.yaml or the systemd unit files on worker nodes. To remediate this finding, edit the kubelet config and/or systemd service directly on each worker node as described in the Manual Steps section.Automation
Automation

