Troubleshooting a misconfigured kublete
Troubleshooting a misconfigured kublete#
- A
Kubleteis the agent that runs in the nodes that directly communicates with theApiserverreceiving instructions from the control node as apodspec. - The kubelet receives a podspec which is a YAML file from the apiserver that describes how the containers should be running. The kublet makes sure that the nodes are healthy and ready t
context#
- In this lab, the
kubletein node01 is not working and you can confirm that by getting to the node01 and checking the kubelet service status
$ ssh node01
$ systemctl status kubelet
# for older systems
$ service status kubelet
- With the kubelet down, this means that we are unable to know the state of our node. This makes it impossible to schedule any pod on it.
- Get the logs to see any issues raised
$ cat /var/log syslog | grep -i kubelet
# or
$ journalctl -xe | kubelet
This should give all logs related to the kubelet and why it failed
fix#
- In this lab, the error is in the flags. we need to make edits to the kubeadm configuration.
- The easiest way to know what configuration file to work with is to use the
findcommand then filter usinggrep
$ find / | grep -i kubeadm
# make edits to the file containinig the `flag`
$ vi /var/lib/kubelet/kubeadm-flags.env
#reload the service
$ systemctl restart kubelet
# confirm the service is running
$ systemctl status kubelet