<p>I have a error when i want to access to my pod:</p>

<p><strong>error: unable to upgrade connection: pod does not exist</strong></p>

<p>it's a cluster with 3 nodes, below some details. Thanks in advance</p>

<pre class="lang-sh prettyprint-override"><code>root@kubm:~/deploy/nginx# kubectl get nodes -o wide

NAME       STATUS   ROLES    AGE   VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION      CONTAINER-RUNTIME

kubm       Ready    master   37h   v1.17.0   10.0.2.15     &lt;none&gt;        Ubuntu 16.04.6 LTS   4.4.0-150-generic   docker://19.3.5

kubnode    Ready    &lt;none&gt;   37h   v1.17.0   10.0.2.15     &lt;none&gt;        Ubuntu 16.04.6 LTS   4.4.0-150-generic   docker://19.3.5

kubnode2   Ready    &lt;none&gt;   37h   v1.17.0   10.0.2.15     &lt;none&gt;        Ubuntu 16.04.6 LTS   4.4.0-150-generic   docker://19.3.5

root@kubm:~/deploy/nginx# kubectl get pods -o wide
NAME                    READY   STATUS    RESTARTS   AGE   IP           NODE       NOMINATED NODE   READINESS GATES

nginx-59c9f8dff-v7dvg   1/1     Running   0          16h   10.244.2.3   kubnode2   &lt;none&gt;           &lt;none&gt;

root@kubm:~/deploy/nginx# kubectl exec -it nginx-59c9f8dff-v7dvg -- /bin/bash

**error: unable to upgrade connection: pod does not exist**

</code></pre>

maroki
<p>I had the same issue running a cluster with <code>Vagrant</code> and <code>Virtualbox</code> the first time.</p>

<p>Adding <code>KUBELET_EXTRA_ARGS=--node-ip=x.x.x.x</code> where <code>x.x.x.x</code> is your VM's IP in <code>/etc/default/kubelet</code> (this can be part of the provisioning script for example) and then restarting kubelet (<code>systemctl restart kubelet</code>) fixes the issues.</p>

<p>This is the recommended way to add extra runtime arguments to <code>kubelet</code> as you can see in <code>/etc/systemd/system/kubelet.service.d/10-kubeadm.conf</code>. Alternatively you can also edit the <code>kubelet</code> config file under <code>/etc/kubernetes/kubelet.conf</code></p>
