Kubeadm join getting error getsockopt: no route to host
After installing the master node I went to add some nodes into our cluster and recieved an error. This is the error I received:
[root@fuselaxnode2 ~]# kubeadm join 10.230.107.137:6443 --token TOKEN --discovery-token-ca-cert-hash sha256:SHA_HASH
[preflight] Running pre-flight checks.
[WARNING FileExisting-crictl]: crictl not found in system path
Suggestion: go get github.com/kubernetes-incubator/cri-tools/cmd/crictl
[discovery] Trying to connect to API Server "10.230.107.137:6443"
[discovery] Created cluster-info discovery client, requesting info from "https://199.230.107.137:6443"
[discovery] Failed to request cluster info, will try again: [Get https://10.230.107.137:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp 10.230.107.137:6443: getsockopt: no route to host]
[discovery] Failed to request cluster info, will try again: [Get https://10.230.107.137:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp 10.230.107.137:6443: getsockopt: no route to host]
[discovery] Failed to request cluster info, will try again: [Get https://10.230.107.137:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp 10.230.107.137:6443: getsockopt: no route to host]
I’m running the following software versions
CentOS 7.4
Kubernetes 1.10.2
I’m getting no route to host. I can ping the master, as well as ssh from the node to the master.
So what is the issue?
The issue is that you have a firewall running on your master node that should be disabled. It’s blocking incoming traffic. If you used my Quick Kubernetes setup guide I mention to make sure that you disabled the host based firewall.
If you forgot, this is your issue. So please issue the following commands on your server.
systemctl disable firewalld systemctl stop firewalld
After running those commands on your master, now go back to the node and attempt to join again.
That should resolve your issue.