title: kubelet saying node "master01" not found
body: <p>I try to stack up my <em>kubeadm</em> cluster with <strong>three</strong> masters. I receive this problem from my <em>init</em> command...</p>
  
  <pre><code>[kubelet-check] Initial timeout of 40s passed.
  
  Unfortunately, an error has occurred:
      timed out waiting for the condition
  
  This error is likely caused by:
      - The kubelet is not running
      - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
  
  If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
      - 'systemctl status kubelet'
      - 'journalctl -xeu kubelet'
  
  Additionally, a control plane component may have crashed or exited when started by the container runtime.
  To troubleshoot, list all containers using your preferred container runtimes CLI, e.g. docker.
  Here is one example how you may list all Kubernetes containers running in docker:
      - 'docker ps -a | grep kube | grep -v pause'
      Once you have found the failing container, you can inspect its logs with:
      - 'docker logs CONTAINERID'
  error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
  </code></pre>
  
  <p>But I do not use no cgroupfs but <strong>systemd</strong>
  And my kubelet complain for not knowing his nodename.</p>
  
  <pre><code>Jan 23 14:54:12 master01 kubelet[5620]: E0123 14:54:12.251885    5620 kubelet.go:2266] node "master01" not found
  Jan 23 14:54:12 master01 kubelet[5620]: E0123 14:54:12.352932    5620 kubelet.go:2266] node "master01" not found
  Jan 23 14:54:12 master01 kubelet[5620]: E0123 14:54:12.453895    5620 kubelet.go:2266] node "master01" not found
  </code></pre>
  
  <p>Please let me know where is the issue.</p>