How is your CNI plugin doing? Assuming you installed flannel based on some of the logs you posted.
kubectl get pods -n kube-system
Hi Macintosh,
Here is the output of command. how to check cni plugin.
[root@localhost ~]# kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-86c58d9df4-q5x9b 1/1 Running 4 4d22h
coredns-86c58d9df4-qzwd7 1/1 Running 4 4d22h
etcd-localhost.localdomain 1/1 Running 10 4d22h
kube-apiserver-localhost.localdomain 1/1 Running 10 4d22h
kube-controller-manager-localhost.localdomain 1/1 Running 45 4d22h
kube-flannel-ds-amd64-2cllh 1/1 Running 8 4d21h
kube-flannel-ds-amd64-gl6rf 1/1 Running 7 4d21h
kube-proxy-lj2sv 1/1 Running 9 4d22h
kube-proxy-tql6m 1/1 Running 4 4d22h
kube-scheduler-localhost.localdomain 1/1 Running 44 4d22h
weave-net-f8sng 2/2 Running 13 4d22h
weave-net-zwjzp 2/2 Running 22 4d22h
kubectl logs weave-net-f8sng -n kube-system
i get this error.
[root@localhost ~]# kubectl logs weave-net-f8sng -n kube-system
Error from server (BadRequest): a container name must be specified for pod weave-net-f8sng, choose one of: [weave weave-npc]
Forgot weave ran multiple containers try this, kubectl logs weave-net-f8sng --all-containers=true -n kube-system
Hi, Your CNI is not happy 
Are you running two CNIs ?
- I can see both
flannelandweave-netfrom yourkubectl get pods -n kube-systemoutput. - Vagrant /VirtualBox combination have issues with networking especially when a NAT interface comes into the picture.
- If you are trying to setup k8s using vagrant - give it a try with GitHub - ansilh/k8s-vagrant: Single Master - Multi Worker K8S cluster for learning and development and see what you can find.