From 3b2781a70c94608390a505a31241ff37118e4f33 Mon Sep 17 00:00:00 2001 From: Anubhav Date: Fri, 11 May 2018 13:07:26 -0700 Subject: [PATCH] Users should choose network plugin before initializing cluster (#8373) Before running `kubeadm init` users should be informed that the command might change depending on the network plugins they choose. It is better to provide it before presenting with `kubeadm init` so that they don't have to tear the cluster apart once they figure out they needed some extra parameters while running the command --- content/en/docs/setup/independent/create-cluster-kubeadm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/setup/independent/create-cluster-kubeadm.md b/content/en/docs/setup/independent/create-cluster-kubeadm.md index 2dad950300..16a0f8bb8d 100644 --- a/content/en/docs/setup/independent/create-cluster-kubeadm.md +++ b/content/en/docs/setup/independent/create-cluster-kubeadm.md @@ -115,7 +115,7 @@ 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). -To initialize the master, pick one of the machines you previously installed +To initialize the master, first choose the pod network plugin you want and check if it requires any parameters to be passed to kubeadm while initializing the cluster. Pick one of the machines you previously installed kubeadm on, and run: ```bash