Kubelet configuration is the node-local YAML data that controls how kubelet operates. The usual file is /var/lib/kubelet/config.yaml, containing cluster DNS settings, certificates for API authentication, the cluster domain, and health endpoints. section 6.2.2 section 8.2.2
Use the configuration file when:
- A kubelet fails to start, inspect /var/lib/kubelet/config.yaml for misconfiguration before investigating broader node problems. section 8.2.2
- A cluster DNS change is required, update the kubelet configuration and account for its role in creating CoreDNS pods and injecting DNS configuration. section 6.2.2
- Access problems involve authentication, distinguish config.yaml from /etc/kubernetes/kubelet.conf, which is the kubelet kubeconfig. section 8.2.2
Reload a changed configuration
After changing kubelet configuration, run systemctl daemon-reload and then systemctl restart kubelet. Verify the service with systemctl status kubelet and inspect failures with journalctl -u kubelet. section 8.2.2
root@kind-control-plane:~# systemctl daemon-reload root@kind-control-plane:~# systemctl restart kubelet
Use the representative daemon reload and kubelet restart commands as a quick operational reference after configuration changes. section 8.2.2
