Skip to content

PV lifecycle states

In Kubernetes, a PersistentVolume (PV) transitions through specific lifecycle phases that reflect its availability and binding status. These states determine whether a volume is free for use, currently allocated, or undergoing reclamation.^[400-devops__06-Kubernetes__k8s-ithelp__Day20__README.md]

Available

A PersistentVolume is in the Available state when it is free and ready to be claimed^[400-devops__06-Kubernetes__k8s-ithelp__Day20__README.md]. In this phase, the storage resource is part of the cluster but has not yet been bound to a PersistentVolumeClaim (PVC).^[400-devops__06-Kubernetes__k8s-ithelp__Day20__README.md]

Bound

The Bound state indicates that the PersistentVolume has been successfully tied to a specific PVC^[400-devops__06-Kubernetes__k8s-ithelp__Day20__README.md]. Once this binding occurs, the volume is considered allocated and is in use by the claim that requested it^[400-devops__06-Kubernetes__k8s-ithelp__Day20__README.md].

Released

A volume enters the Released state when the associated PersistentVolumeClaim has been deleted, but the underlying storage has not yet been reclaimed by the cluster^[400-devops__06-Kubernetes__k8s-ithelp__Day20__README.md]. During this phase, the data may still exist on the storage medium, but the volume is not available for new claims until reclamation is complete^[400-devops__06-Kubernetes__k8s-ithelp__Day20__README.md].

Failed

The Failed state signifies that the automatic reclamation process for the volume has encountered an error^[400-devops__06-Kubernetes__k8s-ithelp__Day20__README.md]. This status indicates that the cluster was unable to successfully recover the storage resource for reuse after it was released^[400-devops__06-Kubernetes__k8s-ithelp__Day20__README.md].

Sources

  • 400-devops__06-Kubernetes__k8s-ithelp__Day20__README.md