# Why is kubelet.conf missing from the output of kubeadm certs check-expiration?

Kubernetes, Hard (Expert), Security. https://k8wiz.com/uquiz/why-is-kubeletconf-missing-from-the-output-of-kubeadm-certs-check-expiration

- A. kubeadm stores the kubelet client certificate inside the cluster CA bundle
- B. kubelet.conf uses a bootstrap token, so it contains no certificate at all
- C. The kubelet certificate is signed by front-proxy-ca, which kubeadm skips
- D. kubeadm leaves it to the kubelet, which rotates its own client certificate

**Answer:** kubeadm leaves it to the kubelet, which rotates its own client certificate

**Explanation:** kubeadm configures the kubelet for automatic client certificate rotation, with kubelet.conf pointing at /var/lib/kubelet/pki/kubelet-client-current.pem. The kubeadm source explicitly excludes kubelet.conf from renewal because management of that certificate is delegated to the kubelet. The bootstrap token from kubeadm join only gets the kubelet its first certificate.
