If you are setting up a k8s cluster using
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 10.32.0.2 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
master node is unable to locate it.