<p>I am using Ubuntu bionic (18.04) with latest version of kubeadm on Ubuntu's repositories (1.13.4) and calico 3.6, following their documentation for "Installing with the Kubernetes API datastore—50 nodes or less" (<a href="https://docs.projectcalico.org/v3.6/getting-started/kubernetes/installation/calico" rel="nofollow noreferrer">https://docs.projectcalico.org/v3.6/getting-started/kubernetes/installation/calico</a>).</p>

<p>It was started with:</p>

<pre><code>sudo kubeadm init --pod-network-cidr=192.168.0.0/16
</code></pre>

<p>But when I apply calico.yaml my node gets stuck with the condition:</p>

<blockquote>
  <p>Conditions:   Type             Status  LastHeartbeatTime<br>
  LastTransitionTime                Reason                       Message
  ----             ------  -----------------                 ------------------                ------                       -------   MemoryPressure   False   Mon, 15 Apr 2019 20:24:43 -0300   Mon, 15 Apr
  2019 20:21:20 -0300   KubeletHasSufficientMemory   kubelet has
  sufficient memory available   DiskPressure     False   Mon, 15 Apr
  2019 20:24:43 -0300   Mon, 15 Apr 2019 20:21:20 -0300<br>
  KubeletHasNoDiskPressure     kubelet has no disk pressure<br>
  PIDPressure      False   Mon, 15 Apr 2019 20:24:43 -0300   Mon, 15 Apr
  2019 20:21:20 -0300   KubeletHasSufficientPID      kubelet has
  sufficient PID available   Ready            False   Mon, 15 Apr 2019
  20:24:43 -0300   Mon, 15 Apr 2019 20:21:20 -0300   KubeletNotReady<br>
  runtime network not ready: NetworkReady=false
  reason:NetworkPluginNotReady message:docker: network plugin is not
  ready: cni config uninitialized</p>
</blockquote>

<p>When I see the system pods (<code>kubectl get pods -n kube-system</code>) I get:</p>

<pre><code>NAME                                       READY   STATUS     RESTARTS   AGE
calico-kube-controllers-55df754b5d-zsttg   0/1     Pending    0          34s
calico-node-5n6p2                          0/1     Init:0/2   0          35s
coredns-86c58d9df4-jw7wk                   0/1     Pending    0          99s
coredns-86c58d9df4-sztxw                   0/1     Pending    0          99s
etcd-cherokee                              1/1     Running    0          36s
kube-apiserver-cherokee                    1/1     Running    0          46s
kube-controller-manager-cherokee           1/1     Running    0          59s
kube-proxy-22xwj                           1/1     Running    0          99s
kube-scheduler-cherokee                    1/1     Running    0          44s
</code></pre>

<p>May this be a bug or there is something missing?</p>

<p>Try removing the taint on the master node, <code>kubectl taint nodes --all node-role.kubernetes.io/master-</code>.</p>

<p>Reference here, <a href="https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/#control-plane-node-isolation" rel="nofollow noreferrer">https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/#control-plane-node-isolation</a></p>
