Worker nodes not ready after installing CNI and Weave

Kubernetes
#1

Hi After following through steps 1-12 to install a k8s cluster, I am still not able to get the worker nodes in the ready state. Here are the outputs of the
$ Kubectl describe node
…
Ready False Tue, 31 Mar 2020 02:27:02 +0000 Mon, 30 Mar 2020 16:47:09 +0000 KubeletNotReady runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
…

vagrant@master-1:~$ kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-69cbb76ff8-6d9ww 0/1 Pending 0 5h33m
coredns-69cbb76ff8-vzd2r 0/1 Pending 0 5h33m
weave-net-lsw2p 1/2 CrashLoopBackOff 96 6h17m
weave-net-zq7wh 1/2 CrashLoopBackOff 94 6h17m

$ kubectl logs weave-net-lsw2p -n kube-system -c weave-npc
…
ERROR: logging before flag.Parse: E0331 02:33:07.833036 1739 reflector.go:205] github.com/weaveworks/weave/prog/weave-npc/main.go:322: Failed to list *v1.NetworkPolicy: Get https://10.96.0.1:443/apis/networking.k8s.io/v1/networkpolicies?limit=500&resourceVersion=0: dial tcp 10.96.0.1:443: connect: no route to host

#2

Can you also post the logs from the running container on the weave pod?

#3

I assume you are asking for the logs of the weave pod. If so, here it is
vagrant@master-1:~$ kubectl logs weave-net-lsw2p -n kube-system -c weave > weave-pod.log
vagrant@master-1:~$ cat !$
cat weave-pod.log
FATA: 2020/03/31 04:53:03.610252 [kube-peers] Could not get peers: Get https://10.96.0.1:443/api/v1/nodes: dial tcp 10.96.0.1:443: connect: no route to host
Failed to get peers

#4

BTW, here are the routing table and interface info for worker node 1
vagrant@worker-1:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.0.2.2 0.0.0.0 UG 100 0 0 enp0s3
10.0.2.0 0.0.0.0 255.255.255.0 U 0 0 0 enp0s3
10.0.2.2 0.0.0.0 255.255.255.255 UH 100 0 0 enp0s3
10.96.0.0 0.0.0.0 255.255.255.0 U 0 0 0 enp0s8
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
192.168.5.0 0.0.0.0 255.255.255.0 U 0 0 0 enp0s8

vagrant@worker-1:~$ ifconfig
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:e1:ae:2a:36 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.0.2.15 netmask 255.255.255.0 broadcast 10.0.2.255
inet6 fe80::39:67ff:fe45:9ce6 prefixlen 64 scopeid 0x20
ether 02:39:67:45:9c:e6 txqueuelen 1000 (Ethernet)
RX packets 1285 bytes 110756 (110.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1285 bytes 122384 (122.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

enp0s8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.5.21 netmask 255.255.255.0 broadcast 192.168.5.255
inet6 fe80::a00:27ff:fea6:aab5 prefixlen 64 scopeid 0x20
ether 08:00:27:a6:aa:b5 txqueuelen 1000 (Ethernet)
RX packets 51636 bytes 20001054 (20.0 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 47079 bytes 5046335 (5.0 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 150317 bytes 9354208 (9.3 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 150317 bytes 9354208 (9.3 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

#5

Any thoughts on this issue? I am still not able to get nodes in the ready state.

#6

Anyone reach any solution to this issue. I too try to implement a home lab and stuck with the same problem.