kubeadm init hangs with --apiserver-advertise-address flag

[Wenzhao Zhang]

Hello Everyone:

I'm setting up a Kubernetes cluster on a few VMs, via using kubeadm. The VMs environment is based on OpenStack, every VM has a private IP and a public IP. I use Ubuntu16.04 64bit.

If I just execute kubeadm init, it can finish without problem. But after I initialize the WEB-UI, I cannot access the web remotely, I think this is because kubeadm init by defaul uses the private IP.

So, I tried kubeadm init with the flag --apiserver-advertise-address and the public IP. But the program just hangs there for hours. I really cannot figure out where is the problem.

Could anyone please help?

Thanks

[david.r...@gmail.com]

Hi there - did you find a solution to this problem? - same thing happening for me using Hypriot on a Raspberry PI. Tried some of the suggestions found here but nothing has worked so far: https://github.com/kubernetes/kubernetes/issues/43800

Any help appreciated.

[Robert Bailey]

Is the public IP passed in via --apiserver-advertise-address reachable from the machine on which you run kubeadm init? I did some testing on GCP last week where a firewall rule was blocking access to the advertise address address and kubeadm init hung forever waiting for the apiserver to come up. 

--
You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.