From 071904cabf35036628ed7c98dd15559eb7f4ad3a Mon Sep 17 00:00:00 2001 From: Di Xu Date: Tue, 12 Jun 2018 01:03:27 +0800 Subject: [PATCH] kubeadm: add a notice on architecture different nodes (#8910) --- content/en/docs/setup/independent/create-cluster-kubeadm.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/en/docs/setup/independent/create-cluster-kubeadm.md b/content/en/docs/setup/independent/create-cluster-kubeadm.md index 78b9f06742..9dfa50f7b6 100644 --- a/content/en/docs/setup/independent/create-cluster-kubeadm.md +++ b/content/en/docs/setup/independent/create-cluster-kubeadm.md @@ -151,6 +151,9 @@ components. This may take several minutes. - 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/)), 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: