kubernetes api server not automatically start after master reboots
Kubelet is not started because of port already in use and hence not able to create pod for api server.Use following command to find out which process is holding the port 10250
root@master admin]# ss -lntp | grep 10250LISTEN 0 128 :::10250 :::* users:(("kubelet",pid=23373,fd=20))It will give you PID of that process and name of that process. If it is unwanted process which is holding the port, you can always kill the process and that port becomes available to use by kubelet.
After killing the process again run the above command, it should return no value.
Just to be on safe side run kubeadm reset and then run kubeadm init and it should go through
Edit:
Using snap stop kubelet did the trick of stopping kubelet on the node.