From dbc615e862335cbaed8a82582e755c0b28a2fb50 Mon Sep 17 00:00:00 2001 From: Andrew Chen Date: Thu, 26 Jan 2017 15:13:51 -0800 Subject: [PATCH] Reimplementing #1708 PR #1708 was Tech LGTM'ed, but the CLA needed to be re-signed (the new CLA needed to be signed), so I'm reimplementing the changes here. --- docs/getting-started-guides/kubeadm.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/getting-started-guides/kubeadm.md b/docs/getting-started-guides/kubeadm.md index 1765e0a1f4..40827c8825 100644 --- a/docs/getting-started-guides/kubeadm.md +++ b/docs/getting-started-guides/kubeadm.md @@ -113,9 +113,9 @@ To initialize the master, pick one of the machines you previously installed `kub # kubeadm init **Note:** this will autodetect the network interface to advertise the master on as the interface with the default gateway. -If you want to use a different interface, specify `--api-advertise-addresses=` argument to `kubeadm init`. +If you want to use a different interface, specify `--api-advertise-addresses ` argument to `kubeadm init`. -If you want to use [flannel](https://github.com/coreos/flannel) as the pod network, specify `--pod-network-cidr=10.244.0.0/16` if you're using the daemonset manifest below. _However, please note that this is not required for any other networks besides Flannel._ +If you want to use [flannel](https://github.com/coreos/flannel) as the pod network, specify `--pod-network-cidr 10.244.0.0/16` if you're using the daemonset manifest below. _However, please note that this is not required for any other networks besides Flannel._ Please refer to the [kubeadm reference doc](/docs/admin/kubeadm/) if you want to read more about the flags `kubeadm init` provides.