liveBook · Manning

Released status

As explained in Kubernetes in Action, Second Edition

Released is a PersistentVolume status indicating that its previous claim has been deleted while the volume may still contain data requiring administrator handling.

Released is a PersistentVolume status reached after its PersistentVolumeClaim is deleted. The volume is no longer bound, but it may still contain data that requires administrator review. section 10.3.3

A new claim does not automatically bind to a Released volume. The retained claim name signals which data was previously attached and helps an administrator decide whether it is safe to remove. section 10.3.3

From Bound to Released

After deleting the quiz-local Pod and quiz-data-local PersistentVolumeClaim, inspect the volume with kubectl get pv. A statically provisioned volume using Retain shows STATUS Released and still lists default/quiz-data-local in CLAIM. Recreating the claim leaves both the claim and Pod Pending until the volume is prepared for reuse. section 10.3.3

How Kubernetes in Action, Second Edition covers it

How deep it goes
Explains the Bound-to-Released transition, failed rebinding, and object recreation, but stops short of detailed cleanup commands.
Examples
Demonstrates quiz-local resources and kubectl output showing Retain, Released, the previous claim, and Pending rebinding.
What you can do after
Operate/configure PersistentVolumes by recognizing Released status and identifying when administrator preparation is required before reuse.
How it connects
Connects PersistentVolume, PersistentVolumeClaim, reclaim policy, Retain, dynamic provisioning, and static provisioning.
Cover of Kubernetes in Action, Second Edition
liveBookmanning.com
Read Kubernetes in Action, Second Edition on liveBook Get the book at manning.com

This explainer was generated by Manning's knowledge graph from the text of Kubernetes in Action, Second Edition. The section links point to the parts of the book it draws on.