From 32c2a7d29ffc5a2e5f6d20a3bdfd56832f1833ac Mon Sep 17 00:00:00 2001 From: Chris Marino Date: Wed, 26 Oct 2016 13:36:31 -0700 Subject: [PATCH] Client glitch again --- docs/getting-started-guides/kubeadm.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/getting-started-guides/kubeadm.md b/docs/getting-started-guides/kubeadm.md index be600d15bd..5848fbdc5f 100644 --- a/docs/getting-started-guides/kubeadm.md +++ b/docs/getting-started-guides/kubeadm.md @@ -158,6 +158,7 @@ This will remove the "dedicated" taint from any nodes that have it, including th You must install a pod network add-on so that your pods can communicate with each other. + **It is necessary to do this before you try to deploy any applications to your cluster, and before `kube-dns` will start up. Note also that `kubeadm` only supports CNI based networks and therefore kubenet based networks will not work.** Several projects provide Kubernetes pod networks using CNI, some of which also support [Network Policy](/docs/user-guide/networkpolicies/). See the [add-ons page](/docs/admin/addons/) for a complete list of available network add-ons.