PersistentVolumeClaim (PVC) definition in Kubernetes - Step-by-Step Execution

Process Flow - PersistentVolumeClaim (PVC) definition

Write PVC YAML

↓

kubectl apply PVC

↓

Kubernetes API Server receives

↓

PVC stored in etcd

↓

PVC status: Pending

↓

Controller finds matching PV

↓

Bind PV to PVC

↓

PVC status: Bound

↓

Pod uses PVC to mount storage

This flow shows how a PVC is defined, applied, matched to a PV, and then bound for use by a pod.

Execution Sample

Kubernetes

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: my-pvc
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi

This YAML defines a PVC requesting 1Gi storage with ReadWriteOnce access mode.

Process Table

Step	Action	Evaluation	Result
1	Write PVC YAML file	YAML valid	PVC definition ready
2	Run 'kubectl apply -f pvc.yaml'	kubectl sends request	PVC object created in cluster
3	API Server stores PVC	PVC stored in etcd	PVC status is Pending
4	Controller checks for matching PV	Find PV with >=1Gi and ReadWriteOnce	PV found and bound to PVC
5	PVC status updated	PVC status changes to Bound	PVC ready for pod use
6	Pod mounts PVC volume	Pod uses PVC name	Pod has persistent storage mounted
7	End	PVC bound and usable	Process complete

💡 PVC is bound to a matching PV and ready for pod usage

Status Tracker

Variable	Start	After Step 3	After Step 5	Final
PVC.status.phase	None	Pending	Bound	Bound
PVC.spec.resources.requests.storage	None	1Gi	1Gi	1Gi
PVC.spec.accessModes[0]	None	ReadWriteOnce	ReadWriteOnce	ReadWriteOnce

Key Moments - 3 Insights

Why does the PVC status start as Pending?

At step 3 in the execution_table, the PVC is created but not yet matched to a PersistentVolume, so its status is Pending until a suitable PV is found and bound.

What does 'Bound' status mean for a PVC?

As shown in step 5, 'Bound' means the PVC has been successfully matched and linked to a PersistentVolume, making the storage ready for use by pods.

Can a pod use a PVC before it is Bound?

No, according to step 6, the pod can only mount the PVC after its status is Bound, ensuring the storage is allocated and available.

Visual Quiz - 3 Questions

Look at the execution_table, what is the PVC status after step 3?

A Released

B Bound

C Pending

D Lost

💡 Hint

Check the 'Result' column at step 3 in the execution_table.

At which step does the PVC become ready for pod use?

A Step 5

B Step 3

C Step 2

D Step 1

💡 Hint

Look for when PVC status changes to Bound in the execution_table.

If the requested storage was increased to 5Gi, what would change in the execution_table?

A Step 6 would be skipped

B Step 4 would look for PV with >=5Gi

C Step 3 PVC status would be Bound immediately

D No changes at all

💡 Hint

Refer to step 4 where the controller finds a matching PV based on requested storage.

Concept Snapshot

PersistentVolumeClaim (PVC) is a request for storage in Kubernetes.
Define PVC in YAML with accessModes and storage size.
Apply with kubectl to create PVC object.
PVC status starts Pending until matched to a PersistentVolume (PV).
Once Bound, pods can mount the PVC for persistent storage.

Full Transcript

This visual execution traces the lifecycle of a PersistentVolumeClaim (PVC) in Kubernetes. First, a PVC YAML is written specifying storage size and access mode. When applied with kubectl, the PVC object is created and stored in the cluster with status Pending. The controller then searches for a matching PersistentVolume (PV) that meets the requested size and access mode. Once found, the PV is bound to the PVC, updating its status to Bound. Finally, pods can mount the PVC to use the persistent storage. Key moments include understanding the Pending and Bound statuses and knowing that pods can only use PVCs after they are Bound.