From a031d03501203986b28f6173aa70a6caca871d0c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tom=C3=A1=C5=A1=20Kukr=C3=A1l?= Date: Mon, 15 Oct 2018 21:23:13 +0200 Subject: [PATCH] use etcd endpoint from advertise-client-urls It makes more sense to use advertised etcd endpoints instead of using listened client URLS. I'm solving this use case: Listen on localhost and public IP but I don't want to add multiple endpoints to kube-apiservers because it's targeting same etcd server. --- cmd/kubeadm/app/phases/controlplane/manifests.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cmd/kubeadm/app/phases/controlplane/manifests.go b/cmd/kubeadm/app/phases/controlplane/manifests.go index 3303e0a0702..34ee45e500f 100644 --- a/cmd/kubeadm/app/phases/controlplane/manifests.go +++ b/cmd/kubeadm/app/phases/controlplane/manifests.go @@ -187,7 +187,7 @@ func getAPIServerCommand(cfg *kubeadmapi.InitConfiguration) []string { // Apply user configurations for local etcd if cfg.Etcd.Local != nil { - if value, ok := cfg.Etcd.Local.ExtraArgs["listen-client-urls"]; ok { + if value, ok := cfg.Etcd.Local.ExtraArgs["advertise-client-urls"]; ok { defaultArguments["etcd-servers"] = value } }