kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Reworked language...

reviewable/pr1549/r6
Chris Marino 2016-10-26 08:00:29 -07:00
parent a600ad20e6
commit 714440f3ae
1 changed files with 1 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/getting-started-guides/kubeadm.md
View File

@ -158,9 +158,6 @@ 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.
Note: Kubeadm only supports CNI based networks and therefore kubenet based networks will not work.
**It is necessary to do this before you try to deploy any applications to your cluster, and before `kube-dns` will start up.**
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.
@ -169,7 +166,7 @@ You can install a pod network add-on with the following command:
# kubectl apply -f <add-on.yaml>
daemonset "<add-on>" created
If you prefer one of the other network providers please refer to their respective installation guides. You should only install one pod network per cluster.
Please refer to the specific add-on installation guide for exact details. You should only install one pod network per cluster.
If you are on another architecture than amd64, you should use the flannel overlay network as described in [the multi-platform section](#kubeadm-is-multi-platform)