If you are setting up a k8s cluster using Vagrant and kubeadm , you may have encountered a problem where master node is somehow unable to locate a pod that is running on another worker node within the same cluster.

vagrant@kubemaster1:~$ kubectl get poNAME           READY   STATUS    RESTARTS   AGE   IP          NODE          NOMINATED NODE   READINESS GATEScka-node-app   1/1     Running   0          84s   kubeworker2   <none>           <none>

vagrant@kubemaster1:~$ kubectl exec -it cka-node-app -- sh
error: unable to upgrade connection: pod does not exist

cka-node-app is definitely running on kubeworker2 but master node is unable to locate it.

Jian Hao

Software engineer obsessed with system reliability. https://www.linkedin.com/in/jianhaot/

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store