Opscraft
Kubernetes troubleshooting · Lesson 7 of 11 · 3 min read

Storage problems

PVC stuck Pending

kubectl describe pvc data-orders-0 -n shop
kubectl get storageclass
  • No default StorageClass, or the named class doesn't exist.
  • Provisioner (EBS CSI driver) not installed, or its controller lacks IAM permissions (IRSA/Pod Identity) → events show failed to provision volume.
  • WaitForFirstConsumer — PVC stays Pending until a pod uses it (that's normal).
  • Requested access mode unsupported (EBS can't do ReadWriteMany — use EFS).
Enlarge diagramWaiting for a pod?WaitForFirstConsumer:normalStorageClassexists? default set?CSI driverinstalled, has IAMpermissions?Access modeEBS cannot doReadWriteMany1234
Figure 1. A PVC stuck Pending: check in this order.
Swipe sideways to see all of it, or tap to open it full screen.

Multi-Attach and AZ issues

  • Multi-Attach error for volume ... Volume is already exclusively attached to one node — an RWO EBS volume is still attached to the old node (node died, pod rescheduled). Usually resolves after the attach/detach controller times out (~6 min); delete the old pod/VolumeAttachment if stuck, and avoid RWO volumes in Deployments with >1 replica.
  • Pod with an EBS PVC can't move to another AZ — EBS is zonal. After an AZ failure, the pod can only run in the volume's AZ. Use topology-aware scheduling, keep capacity per AZ, and for HA rely on application-level replication (databases) rather than moving disks.
Enlarge diagramold node (dead)still holds the volumeEBS volumeReadWriteOnce, AZ-anew podMulti-Attach errorClears when the old attachment is released (about 6 minutes), or detach once the old node is really gone.
Figure 2. Multi-Attach: the EBS volume is still attached to the old node, so the replacement pod on a new node cannot mount it yet.
Swipe sideways to see all of it, or tap to open it full screen.

Volume permissions and capacity

  • permission denied writing to a mounted volume → securityContext.fsGroup so the kubelet sets group ownership, or an init container to chown.
  • Volume full → kubectl exec ... df -h; expand the PVC (allowVolumeExpansion: true, edit spec.resources.requests.storage).