Kubernetes storage · Interactive diagram
Dynamic provisioning: follow the relationships
Press Play for the flow, or Next to study one phase at a time. Scroll horizontally inside the diagram to read its labels. This is a configuration/provisioning flow, not the application's read/write data path.
- 1. Pod uses a claim
The Pod refers to my-data and mounts its storage at /data. This arrow is a configuration reference, not a disk request sent by the Pod.
- 2. PVC names a class
The PVC requests 10Gi and names fast-ssd. The StorageClass is a policy, not the disk itself.
- 3. Class selects the driver
The provisioner field identifies a driver, such as ebs.csi.aws.com. Provisioning timing also depends on volumeBindingMode.
- 4. Provisioner creates storage
The external-provisioner works with the CSI driver to request a real volume from the storage system.
- 5. A PV represents the volume
The provisioner creates a PersistentVolume object that references the new storage. A PV is the Kubernetes representation of that storage.
- 6. PVC and PV bind
Kubernetes binds the claim and volume one-to-one. Scheduling, attachment where needed, and mounting then make the volume usable by the Pod.