vagrant@controlplane:~$ kubectl get pods -A
The connection to the server 192.168.29.105:6443 was refused - did you specify the right host or port? Im trying setup kube adm locally using vagrant and virtual box and Im getting error in master node and the pods are contantly restarting . vagrant@controlplane:~$ sudo crictl ps
WARN[0000] runtime connect using default endpoints: [unix:///run/containerd/containerd.sock unix:///run/crio/crio.sock unix:///var/run/cri-dockerd.sock]. As the default settings are now deprecated, you should set the endpoint instead.
WARN[0000] image connect using default endpoints: [unix:///run/containerd/containerd.sock unix:///run/crio/crio.sock unix:///var/run/cri-dockerd.sock]. As the default settings are now deprecated, you should set the endpoint instead.
CONTAINER IMAGE CREATED STATE NAME ATTEMPT POD ID POD
bae6f47702b4c 505d571f5fd56 14 seconds ago Running kube-proxy 54 c3106444a3e10 kube-proxy-pvnkc
14687dea6a256 c69fa2e9cbf5f 56 seconds ago Running coredns 13 600a5fba632ba coredns-7c65d6cfc9-klgrh
4c5ffc37ba91b 2e96e5913fc06 5 minutes ago Running etcd 44 1a76599abafbb etcd-controlplane
e075a0ededd0b c69fa2e9cbf5f 15 minutes ago Running coredns 8 567a7d8934543 coredns-7c65d6cfc9-cww7d
5f511c47ae8c4 f3fbc66455cbf 15 minutes ago Running weave-npc 15 50dbc37c0080b weave-net-dpgxj
0a7513244f0f9 c0537db9c8833 15 minutes ago Running weave 18 50dbc37c0080b weave-net-dpgxj
This could be due to firewall or network issues. Please check your firewall settings to ensure that the necessary Kubernetes ports are not blocked. Additionally, could you please share the steps you followed or the documentation you referred to for setting up the Kubernetes cluster? In my experience, installing Kubernetes with Vagrant often encounters issues related to network interfaces.
This is also very often due to misconfiguration of containerd during a kubeadm install. Hopefully you’re following the tutorial from the CKA github repo; the Node Setup page explains the issue, and how to fix it.