From 6d9c7babe1eba9fa2f833a960070c011de6328a1 Mon Sep 17 00:00:00 2001 From: Chris Marino Date: Wed, 26 Oct 2016 13:35:41 -0700 Subject: [PATCH] Typos, clarity.... --- docs/getting-started-guides/kubeadm.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/getting-started-guides/kubeadm.md b/docs/getting-started-guides/kubeadm.md index f53c2f9480..be600d15bd 100644 --- a/docs/getting-started-guides/kubeadm.md +++ b/docs/getting-started-guides/kubeadm.md @@ -158,14 +158,13 @@ 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 CNI based network alternatives are available than enable Kubernetes pod networks. Some may 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. +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. You can install a pod network add-on with the following command: # kubectl apply -f - daemonset "" created Please refer to the specific add-on installation guide for exact details. You should only install one pod network per cluster.