<p>I have an AKS Cluster with two nodepools. Node pool 1 has 3 nodes, and nodepool 2 has 1 node - all Linux VMs. I noticed that after stopping the VMs and then doing kubectl get pods, the Pods status shows "running" though the VMs are not actually running. How is this possible?</p>

<p>This is the command I tried: <code>kubectl get pods -n development -o=wide</code></p>

<p>The screenshot is given below. Though VMs are not running, the Pod status shows "running". However, trying to access the app using the Public IP of the service resulted in</p>

<blockquote>
  <p>ERR_CONNECTION_TIMED_OUT</p>
</blockquote>

<p><a href="https://i.stack.imgur.com/CNLKL.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/CNLKL.png" alt="enter image description here"></a></p>

Thomas
<p>Here is a full thread (<a href="https://github.com/kubernetes/kubernetes/issues/55713" rel="nofollow noreferrer">https://github.com/kubernetes/kubernetes/issues/55713</a>) on this issue. The problem here is by default the pod waits for 5 minutes before evicting to another node when the current node becomes <code>notReady</code>, but in this case none of the worker nodes are ready and hence pods are not getting evicted. Refer the git issue, there are some suggestions and solutions provided.</p>
