Issue with setting up Kubeadm master node in Ubuntu VM

2/1/2019

I am stuck with setting up kubeadm in Ubuntu VM (18.04). When i try to run the below command

kubeadm init pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=13.71.XX.XX (My IP) 

Kubeadm fails with error message :

"Unfortunately, an error has occurred: timed out waiting for the condition"

Upon Inspecting docker logs , etcd containers have failed with below message

enter image description here

Any hint where I am going wrong ?

Update : Adding screenshot of ip a & netstat

enter image description here

enter image description here

-- Rangesh
kubeadm
kubernetes

2 Answers

2/15/2019

It looks like the IP address 13.71.XX.XX (My IP) is not configured on any of the interfaces on that host.

All traffic with destination IP A.B.C.D that comes to an interface that doesn't have A.B.C.D configured will be dropped.

The only exception is if you put network interface in promiscuous mode, like the tcpdump program does.

It should work fine if you use any of the IP addresses that are present on host interfaces.

kubeadm init pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=10.0.10.5

Alternatively, you may try to configure 13.71.XX.XX/32 as a secondary IP address on the eth0 interface. Then the following command should also work:

kubeadm init pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=13.71.XX.XX

To successfully join the cluster, the worker node should be able to reach the master node IP address without crossing NAT, which is hardly possible to me in the last case.

-- VAS
Source: StackOverflow

2/1/2019

It appears like port 2380 is blocked on the host. Check to see what is running on that port. You need to make it available for etcd

Can you run kubeadm init without api server address parameter and check

-- P Ekambaram
Source: StackOverflow