Documentation incorrectly said to turn down the cluster instead of tear down the cluster.

reviewable/pr1601/r1
Bill Allen 2016-11-01 20:50:53 +00:00
parent de27c5c194
commit 596a56e3e5
1 changed files with 1 additions and 1 deletions
docs/getting-started-guides

View File

@ -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: