From 596a56e3e5fa85356f03cb7f2da773d9f5bcadf0 Mon Sep 17 00:00:00 2001 From: Bill Allen Date: Tue, 1 Nov 2016 20:50:53 +0000 Subject: [PATCH] Documentation incorrectly said to turn down the cluster instead of tear down the cluster. --- docs/getting-started-guides/kubeadm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started-guides/kubeadm.md b/docs/getting-started-guides/kubeadm.md index 5848fbdc5f..31208e6590 100644 --- a/docs/getting-started-guides/kubeadm.md +++ b/docs/getting-started-guides/kubeadm.md @@ -101,7 +101,7 @@ Note: `setenforce 0` will no longer be necessary on CentOS once [#33555](https:/ The master is the machine where the "control plane" components run, including `etcd` (the cluster database) and the API server (which the `kubectl` CLI communicates with). All of these components run in pods started by `kubelet`. -Right now you can't run `kubeadm init` twice without turning down the cluster in between, see [Turndown](#turndown). +Right now you can't run `kubeadm init` twice without tearing down the cluster in between, see [Tear down](#tear-down). To initialize the master, pick one of the machines you previously installed `kubelet` and `kubeadm` on, and run: