title: kubernetes worker node in "NotReady" status
body: <p>I am trying to setup my first cluster using Kubernetes 1.13.1. The master got initialized okay, but both of my worker nodes are <code>NotReady</code>.  <code>kubectl describe node</code> shows that Kubelet stopped posting node status on both worker nodes.  On one of the worker nodes I get log output like</p>
  
  <pre><code>&gt; kubelet[3680]: E0107 20:37:21.196128    3680 kubelet.go:2266] node
  &gt; "xyz" not found.
  </code></pre>
  
  <p>Here is the full details:</p>
  
  <p>I am using Centos 7 &amp; Kubernetes 1.13.1.</p>
  
  <p>Initializing was done as follows: </p>
  
  <pre><code>[root@master ~]# kubeadm init --apiserver-advertise-address=10.142.0.4 --pod-network-cidr=10.142.0.0/24
  </code></pre>
  
  <p>Successfully initialized the cluster:</p>
  
  <pre><code>You can now join any number of machines by running the following on each node
  as root:
  `kubeadm join 10.142.0.4:6443 --token y0epoc.zan7yp35sow5rorw --discovery-token-ca-cert-hash sha256:f02d43311c2696e1a73e157bda583247b9faac4ffb368f737ee9345412c9dea4`
  </code></pre>
  
  <p>deployed the flannel CNI:</p>
  
  <p><code>kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml</code></p>
  
  <p>The join command worked fine.</p>
  
  <p><code>[kubelet-start] Activating the kubelet service</code>
  <code>[tlsbootstrap] Waiting for the kubelet to perform the TLS Bootstrap...</code>
  <code>[patchnode] Uploading the CRI Socket information "/var/run/dockershim.sock" to the Node API object "node01" as an annotation</code></p>
  
  <blockquote>
    <p>This node has joined the cluster:</p>
  </blockquote>
  
  <pre><code>* Certificate signing request was sent to apiserver and a response was received.
  * The Kubelet was informed of the new secure connection details.
  Run 'kubectl get nodes' on the master to see this node join the cluster.
  </code></pre>
  
  <p>Result of kubectl get nodes:</p>
  
  <pre><code>[root@master ~]# kubectl get nodes
  
  NAME     STATUS     ROLES    AGE   VERSION
  
  master   Ready      master   9h    v1.13.1
  
  node01   NotReady   &lt;none&gt;   9h    v1.13.1
  
  node02   NotReady   &lt;none&gt;   9h    v1.13.1
  </code></pre>
  
  <p>on both nodes:</p>
  
  <p><code>[root@node01 ~]# service kubelet status</code>
  Redirecting to /bin/systemctl status kubelet.service
  ● kubelet.service - kubelet: The Kubernetes Node Agent </p>
  
  <pre><code> Loaded: loaded (/etc/systemd/system/kubelet.service; enabled; vendor preset: disabled)
  
    Drop-In: /etc/systemd/system/kubelet.service.d
             └─10-kubeadm.conf
  
     Active: active (running) since Tue 2019-01-08 04:49:20 UTC; 32s ago
  
       Docs: https://kubernetes.io/docs/
  
   Main PID: 4224 (kubelet)
  
     Memory: 31.3M
  
     CGroup: /system.slice/kubelet.service
             └─4224 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfi
  
  `Jan 08 04:54:10 node01 kubelet[4224]: E0108 04:54:10.957115    4224 kubelet.go:2266] node "node01" not found`
  </code></pre>
  
  <p>I appreciate your advise on how to troubleshoot this.</p>