hard20 pts · first answer countskubernetesstorage

StatefulSet Pod pending after node replacement

After a node group upgrade, one StatefulSet Pod is stuck Pending with the event below. Nodes exist in three zones. What is the cause?

0/6 nodes are available: 3 node(s) had volume node affinity conflict,
3 node(s) didn't match Pod's node affinity/selector.

A.The PVC was deleted during the upgrade and the Pod is waiting for a new disk.B.The PersistentVolume is a zonal disk in a zone where no matching node is available.C.StatefulSet Pods cannot be scheduled while a node group upgrade is in progress.D.The storage class uses reclaimPolicy: Delete, which blocks scheduling on new nodes.

← Running migrations before rollout in Argo CD Java Pod OOMKilled with free heap →