kubeadm join - Failed to request cluster info - getsockopt: no route to host

2,158 views
Skip to first unread message

DK

unread,
Oct 13, 2017, 10:41:14 AM10/13/17
to Kubernetes developer/contributor discussion
Hi,

How can I debug what's going wrong with kubeadm join

kubeadm join --token zzzzzzzzzzzzzz 10.134.30.100:6443 --discovery-token-ca-cert-hash sha256:xxxxxxxx

[kubeadm] WARNING: kubeadm is in beta, please do not use it for production clusters.
[preflight] Running pre-flight checks
[discovery] Trying to connect to API Server "10.134.30.100:6443"
[discovery] Created cluster-info discovery client, requesting info from "https://10.134.30.100:6443"
[discovery] Failed to request cluster info, will try again: [Get https://10.134.30.100:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp 10.134.30.100:6443: getsockopt: no route to host]


I noticed kube-dns  was  Running but I guess after I tried join it went into CrashLoopBackOff

kubectl get pods --all-namespaces
NAMESPACE     NAME                             READY     STATUS             RESTARTS   AGE
kube-system   etcd-master                      1/1       Running            0          24m
kube-system   kube-apiserver-master            1/1       Running            0          24m
kube-system   kube-controller-manager-master   1/1       Running            0          24m
kube-system   kube-dns-545bc4bfd4-pfhxf        1/3       CrashLoopBackOff   15         25m
kube-system   kube-flannel-ds-b6smz            1/1       Running            0          24m
kube-system   kube-proxy-khmnj                 1/1       Running            0          25m
kube-system   kube-scheduler-master            1/1       Running            0          24m

DK

unread,
Oct 13, 2017, 12:14:20 PM10/13/17
to Kubernetes developer/contributor discussion
Disabling firewall on the master solved the issue

systemctl disable firewalld
systemctl stop firewalld

Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages