Home / BeaverDeck / Docs / Insights Guide / Storage Insights / PVC Binding

PVC Binding

BeaverDeck uses this check to identify a specific storage condition that may need operator review.

Permissions: viewing checks requires insights: view. Opening a linked object or logs requires the corresponding resource permission, and the BeaverDeck ServiceAccount must be allowed to read the Kubernetes resources used by the check. Suppressing a finding requires insights: edit and affects all users.

Check type	`pvc-binding`
Insights section	Storage Insights
Alert severity	Critical

When It Reports A Finding

A PersistentVolumeClaim is not in phase Bound or has no spec.volumeName.

Why This Is A Problem

Pods that require the claim may remain Pending or fail to mount storage, preventing the workload from starting.

Recommended Response

Review PVC and Pod events for provisioning, topology, access mode, capacity, or attachment errors.
Check the StorageClass, provisioner, requested size, access modes, volume binding mode, and available backend capacity.
Correct the claim or storage infrastructure and confirm that the PVC reaches Bound before restarting dependent workloads.

Scope And Limitations

There is no grace period. A newly created PVC can be legitimately Pending while dynamic provisioning completes.

After remediation: refresh Storage Insights and verify the underlying resource or metric. Suppress the finding only when the condition is intentional and its risk is accepted.