Back to all scenarios
Scenario #365
Storage
Kubernetes v1.21, NFS

Retained PV Blocks New Claim Binding with Identical Name

A PV stuck in Released state with Retain policy blocked new PVCs from binding with the same name.

Find this helpful?
What Happened

Deleted old PVC and recreated a new one with the same name, but it stayed Pending.

Diagnosis Steps
  • 1PV was in Released, PVC was Pending.
  • 2Events: PVC is not bound.
Root Cause

Retained PV still owned the identity, blocking rebinding.

Fix/Workaround
• Manually deleted the old PV to allow dynamic provisioning.
Lessons Learned

Retain policies require admin cleanup.

How to Avoid
  • 1Use Delete policy for short-lived PVCs.
  • 2Automate orphan PV audits.
Previous ScenarioNext Scenario