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

kubeadm: add a notice on architecture different nodes (#8910)

pull/8747/merge
Di Xu 2018-06-12 01:03:27 +08:00 committed by k8s-ci-robot
parent 70dd13065b
commit 071904cabf
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
content/en/docs/setup/independent/create-cluster-kubeadm.md
View File

@ -151,6 +151,9 @@ components. This may take several minutes.
- You can't run `kubeadm init` twice without tearing down the cluster in between - You can't run `kubeadm init` twice without tearing down the cluster in between
([unless you're upgrading from v1.6 to v1.7](/docs/tasks/administer-cluster/kubeadm-upgrade-1-7/)), ([unless you're upgrading from v1.6 to v1.7](/docs/tasks/administer-cluster/kubeadm-upgrade-1-7/)),
see [Tear Down](#tear-down). see [Tear Down](#tear-down).
- If you join a node with a different architecture to your cluster, you should create a separate
Deployment or DaemonSet for `kube-proxy` and `kube-dns` on the node. This is because the Docker images for these
components do not currently support multi-architecture.
The output should look like: The output should look like: