From b144d991a08a75675cf1f0ee15369ecdd217cfd5 Mon Sep 17 00:00:00 2001 From: xilabao Date: Mon, 20 Mar 2017 13:49:38 +0800 Subject: [PATCH] fix to taint the master node --- docs/getting-started-guides/kubeadm.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/getting-started-guides/kubeadm.md b/docs/getting-started-guides/kubeadm.md index 03cf546eaa..a45c2f1319 100644 --- a/docs/getting-started-guides/kubeadm.md +++ b/docs/getting-started-guides/kubeadm.md @@ -173,10 +173,9 @@ The key is used for mutual authentication between the master and the joining nod By default, your cluster will not schedule pods on the master for security reasons. If you want to be able to schedule pods on the master, for example if you want a single-machine Kubernetes cluster for development, run: - # kubectl taint nodes --all dedicated- - node "test-01" tainted - taint key="dedicated" and effect="" not found. - taint key="dedicated" and effect="" not found. + # MASTER_NODE="actual_master_node_name" + # TAINT_KEY=$(kubectl get no ${MASTER_NODE} --template="{{(index .spec.taints 0).key}}") + # kubectl taint nodes ${MASTER_NODE} ${TAINT_KEY}- This will remove the "dedicated" taint from any nodes that have it, including the master node, meaning that the scheduler will then be able to schedule pods everywhere.