Hello @Kube VS ,
Sorry for late reply here . Are you still seeing the issues ?
Can you start checking below data:
kubectl describe pv, pvc, sc
kubectl describe pod
kubectl describe node
Are you sure , none of your nodes are in Az ?
I am thinking when the new nodes got scaled up with those zone tags and when the new PV which is getting binding to a Pod - that POD might be assigned to one of the node which is in zone.
Hence if the Pod is trying to make use of the PV via PVC , since the underlying node is in a zone - probably that PVC is also having that particular node Affinity.
If you see the corresponding disk provisioned through PVC - you might see that disk is in one of the availability Zone (You can check it in Azure Portal for the disk)
(I was trying to repro locally but I am not able to do so as you are using an older version of kubernetes)
Starting 1.21.* kubernetes has made lot of changes w.r.t provisioner.
Prior to 1.21.* provisioners were: kubernetes.io/azure-disk
with 1.21.* versions default provisioners are disk.csi.azure.com