kubernetes resource_error ai_generated true

persistentvolumeclaim 卡在 Pending 状态

persistentvolumeclaim is stuck in Pending state

ID: kubernetes/pvc-stuck-pending-no-storage-class

其他格式: JSON · Markdown 中文 · English
82%修复率
87%置信度
1证据数
2023-03-01首次发现

版本兼容性

版本状态引入弃用备注
Kubernetes 1.28.x active — — —
Kubernetes 1.29.x active — — —
CSI drivers v1.30.x active — — —

根因分析

PersistentVolumeClaim 无法绑定，因为请求的存储类不存在、Provisioner 未部署或没有可用的匹配 PersistentVolume。

English

The PersistentVolumeClaim cannot bind because the requested storage class does not exist, the provisioner is not deployed, or no matching PersistentVolume is available.

generic

官方文档

https://kubernetes.io/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims

解决方案

  1. 检查 StorageClass 是否存在：`kubectl get storageclass`。如果请求的类（例如 'fast'）缺失，创建它：`kubectl apply -f - <<EOF
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: fast
provisioner: kubernetes.io/aws-ebs
parameters:
  type: gp3
EOF`
  2. 如果使用 CSI 驱动，验证驱动是否部署：`kubectl get csidrivers`。如果缺失，安装驱动（例如 EBS CSI 驱动：`kubectl apply -k "github.com/kubernetes-sigs/aws-ebs-csi-driver/deploy/kubernetes/overlays/stable/?ref=master"`）。
  3. 描述 PVC 以获取详细事件：`kubectl describe pvc <PVC名称> -n <命名空间>`。查找 'waiting for first consumer to be created before binding'，这表示动态配置正在等待 Pod。如果是，创建一个使用该 PVC 的 Pod。

无效尝试

常见但无效的做法:

  1. Delete and recreate the PVC with the same spec. 85% 失败

    Recreating the same PVC without fixing the storage class or provisioner will result in the same Pending state.

  2. Manually create a PersistentVolume without matching the PVC's storage class or size. 70% 失败

    A manually created PV must match the PVC's storage class, access modes, and size (or be larger) to bind. Mismatched PVs will remain unbound.

  3. Set storageClassName to empty string to use default class without verifying existence. 60% 失败

    If no default StorageClass exists, the PVC will still be Pending. Use `kubectl get storageclass` to verify.