Skip to content

Persistent Volume (PV)

A Persistent Volume (PV) is a storage resource within a Kubernetes cluster that represents a piece of storage provisioned by an administrator or dynamically provisioned using Storage Classes^[400-devops-06-kubernetes-k8s-ithelp-day16-readme.md]. It is a cluster-level resource, meaning it exists independently of the individual Pods that utilize it^[400-devops-06-kubernetes-k8s-ithelp-day16-readme.md].

Lifecycle and Independence

Unlike volumes that are tightly coupled to a Pod's lifecycle, a PV has a lifecycle that is independent of any Pod using it^[400-devops-06-kubernetes-k8s-ithelp-day16-readme.md]. This means that even if a Pod is terminated or deleted, the data within the PV persists, ensuring long-term data retention across application restarts or failures^[400-devops-06-kubernetes-k8s-ithelp-day16-readme.md].

Relationship with PersistentVolumeClaim (PVC)

While the PV represents the physical storage resource, users interact with it via a PersistentVolumeClaim (PVC)^[400-devops-06-kubernetes-k8s-ithelp-day16-readme.md]. A PVC acts as a request for storage by a user; analogous to how a Pod consumes Node resources (CPU, RAM), a PVC consumes PV resources^[400-devops-06-kubernetes-k8s-ithelp-day16-readme.md].

Sources

  • 400-devops-06-kubernetes-k8s-ithelp-day16-readme.md