From cb88b43438d0aa2878a10231bb8696c75c91a453 Mon Sep 17 00:00:00 2001 From: hongkunyoo Date: Sat, 17 Nov 2018 02:16:57 +0900 Subject: [PATCH] Adding name arguement in kubeadm-config.yaml (#10948) In AWS cloud platform, omitting the name while initializing etcd cluster causes "Couldn't find local name "$HOSTNAME in the initial cluster configuration" It seems that the etcd tries to find short hostname, not the FQDN hostname. To avoid this, passing the name explicitly to etcd configuration solved the problem. [related issue1](https://github.com/coreos/bugs/issues/2054) [related issue2](https://github.com/kubernetes/kubeadm/issues/653) --- content/en/docs/setup/independent/high-availability.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/en/docs/setup/independent/high-availability.md b/content/en/docs/setup/independent/high-availability.md index 74beb0aa93..6c49266ff3 100644 --- a/content/en/docs/setup/independent/high-availability.md +++ b/content/en/docs/setup/independent/high-availability.md @@ -151,6 +151,7 @@ Optionally replace `stable` with a different version of Kubernetes, for example etcd: local: extraArgs: + name: "CP0_HOSTNAME" listen-client-urls: "https://127.0.0.1:2379,https://CP0_IP:2379" advertise-client-urls: "https://CP0_IP:2379" listen-peer-urls: "https://CP0_IP:2380" @@ -230,6 +231,7 @@ Remember that your config may differ from this example. etcd: local: extraArgs: + name: "CP1_HOSTNAME" listen-client-urls: "https://127.0.0.1:2379,https://CP1_IP:2379" advertise-client-urls: "https://CP1_IP:2379" listen-peer-urls: "https://CP1_IP:2380" @@ -320,6 +322,7 @@ Remember that your config may differ from this example. etcd: local: extraArgs: + name: "CP2_HOSTNAME" listen-client-urls: "https://127.0.0.1:2379,https://CP2_IP:2379" advertise-client-urls: "https://CP2_IP:2379" listen-peer-urls: "https://CP2_IP:2380"