Sanitation teams create new PersistentVolumeClaims that remain Pending while the CSI controller pod crash-loops. What does this indicate?
Select an answer to reveal the explanation.
Short Explanation
Dynamic volumes need the CSI controller's help to call the storage backend—like a permits desk that stamps new claims. If that desk's pod crash-loops, fresh PVCs sit Pending.
Full Explanation
CSI provisioning workflows rely on controller sidecars/pods to create volumes and bind PersistentVolumeClaims. When the CSI controller is unhealthy, newly created PVCs commonly remain Pending. This is distinct from Service routing, scheduler binary presence, or CoreDNS, which are not the primary path for CSI provisioning.