From e6eac66c948093898e337acffa1729aed1c8236b Mon Sep 17 00:00:00 2001 From: Luke Marsden Date: Mon, 26 Sep 2016 15:18:33 +0100 Subject: [PATCH] Include slightly surprising output. --- docs/getting-started-guides/kubeadm.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/getting-started-guides/kubeadm.md b/docs/getting-started-guides/kubeadm.md index 0ed390dae2..22e64fa539 100644 --- a/docs/getting-started-guides/kubeadm.md +++ b/docs/getting-started-guides/kubeadm.md @@ -118,8 +118,11 @@ By default, your cluster will not schedule pods on the master for security reaso 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. -This will remove the "dedicated" taint from all nodes, including the master node, meaning that the scheduler will then be able to schedule pods everywhere. +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. ### (3/4) Joining your nodes