<p>I experiencing some issues when scale down/up ec2 of my k8s cluster. It might happen that sometimes I have new nodes, and old are terminated. k8s version is 1.22</p>
<p>Sometimes some pods are in ContainerCreating state. I am trying to describe pod and see something like this:</p>
<pre><code>Warning FailedAttachVolume 29m attachdetach-controller Multi-Attach error for volume
Warning FailedMount 33s (x13 over 27m) kubelet....
</code></pre>
<p>I am checking that pv exists, pvs exists as well. However on pvc I see annotation <em><strong>volume.kubernetes.io/selected-node</strong></em> and its value refers to the node that already not exist.</p>
<p>When I am editing the pvc and deleting this annotation, everything continue to work.
Another thing that It happens not always, I don't understand why.</p>
<p>I tried to search information, found some couple of links</p>
<p><a href="https://github.com/kubernetes/kubernetes/issues/100485" rel="nofollow noreferrer">https://github.com/kubernetes/kubernetes/issues/100485</a> and
<a href="https://github.com/kubernetes/kubernetes/issues/89953" rel="nofollow noreferrer">https://github.com/kubernetes/kubernetes/issues/89953</a>
however I am not sure that I properly understand this.</p>
<p>Could you please helm me out with this.</p>

<p>Well, as you found out in <a href="https://github.com/kubernetes/kubernetes/issues/100485" rel="nofollow noreferrer">volume.kubernetes.io/selected-node never cleared for non-existent nodes on PVC without PVs #100485</a> - this is a known issue, with no available fix yet.</p>
<p>Until the issue is fixed, as a workaroud, you need to remove <code>volume.kubernetes.io/selected-node</code> annotation manually.</p>
