Welcome to the Linux Foundation Forum!

Lab 3.2. Grow the Cluster: Step 13

Hello,
I am trying to run step 13 in my worker on GCloud and I get the following...

root@worker:~# kubeadm join 10.2.0.8:6443 --token 2ebfx1.kzrqpjy5vks7s2lc --discovery-token-ca-cert-hash sha256:6db9074ee3706111f787d03f9abb8ad19a7fd9dfaca
5e854117c2a12d90c892f  --node-name=worker 
[preflight] Running pre-flight checks
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
error execution phase preflight: unable to fetch the kubeadm-config ConfigMap: failed to get config map: Get "https://k8scp:6443/api/v1/namespaces/kube-system/configmaps/kubeadm-config?timeout=10s": dial tcp: lookup k8scp on 127.0.0.53:53: server misbehaving
To see the stack trace of this error execute with --v=5 or higher

Running it with the stack trace to get more information I get

root@worker:~# kubeadm join 10.2.0.8:6443 --token 2ebfx1.kzrqpjy5vks7s2lc --discovery-token-ca-cert-hash sha256:6db9074ee3706111f787d03f9abb8ad19a7fd9dfaca
5e854117c2a12d90c892f  --node-name=worker 
[preflight] Running pre-flight checks
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
error execution phase preflight: unable to fetch the kubeadm-config ConfigMap: failed to get config map: Get "https://k8scp:6443/api/v1/namespaces/kube-system/configmaps/kubeadm-config?timeout=10s": dial tcp: lookup k8scp on 127.0.0.53:53: server misbehaving
To see the stack trace of this error execute with --v=5 or higher
root@worker:~# kubeadm join k8scp:6443 --token 2ebfx1.kzrqpjy5vks7s2lc --discovery-token-ca-cert-hash sha256:6db9074ee3706111f787d03f9abb8ad19a7fd9dfaca5e854117c2a12d90c892f  --node-name=worker --v=5
I1030 08:37:24.380973    3734 initconfiguration.go:122] detected and using CRI socket: unix:///var/run/containerd/containerd.sock
[preflight] Running pre-flight checks
I1030 08:37:24.381207    3734 preflight.go:93] [preflight] Running general checks
I1030 08:37:24.381279    3734 checks.go:278] validating the existence of file /etc/kubernetes/kubelet.conf
I1030 08:37:24.381295    3734 checks.go:278] validating the existence of file /etc/kubernetes/bootstrap-kubelet.conf
I1030 08:37:24.381316    3734 checks.go:102] validating the container runtime
I1030 08:37:24.411766    3734 checks.go:637] validating whether swap is enabled or not
I1030 08:37:24.411887    3734 checks.go:368] validating the presence of executable crictl
I1030 08:37:24.411935    3734 checks.go:368] validating the presence of executable conntrack
I1030 08:37:24.411970    3734 checks.go:368] validating the presence of executable ip
I1030 08:37:24.412007    3734 checks.go:368] validating the presence of executable iptables
I1030 08:37:24.412045    3734 checks.go:368] validating the presence of executable mount
I1030 08:37:24.412079    3734 checks.go:368] validating the presence of executable nsenter
I1030 08:37:24.412115    3734 checks.go:368] validating the presence of executable ebtables
I1030 08:37:24.412186    3734 checks.go:368] validating the presence of executable ethtool
I1030 08:37:24.412231    3734 checks.go:368] validating the presence of executable socat
I1030 08:37:24.412267    3734 checks.go:368] validating the presence of executable tc
I1030 08:37:24.412297    3734 checks.go:368] validating the presence of executable touch
I1030 08:37:24.412335    3734 checks.go:514] running all checks
I1030 08:37:24.430448    3734 checks.go:399] checking whether the given node name is valid and reachable using net.LookupHost
I1030 08:37:24.442185    3734 checks.go:603] validating kubelet version
I1030 08:37:24.505303    3734 checks.go:128] validating if the "kubelet" service is enabled and active
I1030 08:37:24.520176    3734 checks.go:201] validating availability of port 10250
I1030 08:37:24.520563    3734 checks.go:278] validating the existence of file /etc/kubernetes/pki/ca.crt
I1030 08:37:24.520594    3734 checks.go:428] validating if the connectivity type is via proxy or direct
I1030 08:37:24.520651    3734 join.go:536] [preflight] Discovering cluster-info
I1030 08:37:24.520701    3734 token.go:79] [discovery] Created cluster-info discovery client, requesting info from "k8scp:6443"
I1030 08:37:24.521593    3734 token.go:210] [discovery] Waiting for the cluster-info ConfigMap to receive a JWS signaturefor token ID "2ebfx1"
I1030 08:37:24.592619    3734 token.go:221] [discovery] Retrying due to error: failed to request the cluster-info ConfigMap: Get "https://k8scp:6443/api/v1/namespaces/kube-public/configmaps/cluster-info?timeout=10s": dial tcp: lookup k8scp on 127.0.0.53:53: server misbehaving
I1030 08:37:29.557822    3734 token.go:221] [discovery] Retrying due to error: failed to request the cluster-info ConfigMap: Get "https://k8scp:6443/api/v1/namespaces/kube-public/configmaps/cluster-info?timeout=10s": dial tcp: lookup k8scp on 127.0.0.53:53: server misbehaving

Is there a way of fixing this at all?

Many thanks

Comments

Categories

Upcoming Training