<p>When I restart the docker service in work node, the logs of kubelet in master node report a no such file error.</p>

<pre><code># in work node
# systemctl restart docker service

# in master node
# journalctl -u kubelet
# failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "/var/lib/kubelet/config.yaml", error: open /var/lib/kubelet/config.yaml: no such file or directory
</code></pre>

<p>Arghya is right but I would like to add some info you should be aware of:</p>

<ol>
<li><p>You can execute <code>kubeadm init phase kubelet-start</code> to only invoke a particular step that will write the kubelet configuration file and environment file and then start the kubelet.</p></li>
<li><p>After performing a restart there is a chance that swap would re-enable. Make sure to run <code>swapoff -a</code> in order to turn it off.</p></li>
<li><p>If you encounter any token validation problems than simply run <code>kubeadm token create --print-join-command</code> and than do the join process with the provided info. Remember that tokens expire after 24 hours by default.</p></li>
<li><p>If you wish to know more about <code>kubeadm init phase</code> you can find it <a href="https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init-phase/" rel="noreferrer">here</a> and <a href="https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#instructions" rel="noreferrer">here</a>.</p></li>
</ol>

<p>Please let me know if that helped. </p>
