From 642043cfe147bfb379a830b15bfd3db27a29afb7 Mon Sep 17 00:00:00 2001 From: Nicolas Dextraze Date: Tue, 9 May 2017 15:42:57 -0700 Subject: [PATCH] Fix missing = when setting api advertised address Similar to the pod-network-cird= issue, with no = there is no immediate problem but it causes trouble along the way (i.e. I wasn't able to access the dashboard via kubectl proxy) --- 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 3d9f005e7a..d671571c7d 100644 --- a/docs/getting-started-guides/kubeadm.md +++ b/docs/getting-started-guides/kubeadm.md @@ -158,7 +158,7 @@ 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 `--apiserver-advertise-address ` argument to `kubeadm +interface, specify `--apiserver-advertise-address=` argument to `kubeadm init`. There are pod network implementations where the master also plays a role in