liveBook · Manning

Persistent volume claim

As explained in Effective Platform Engineering

A persistent volume claim is a Kubernetes resource that requests persistent storage with specified capacity and access requirements.

A persistent volume claim requests storage with defined capacity and access requirements, giving workloads a Kubernetes resource for consuming persistent volumes. section 7.4.6

Dynamic EBS claim test

A 4Gi ReadWriteOnce claim targets an EBS CSI StorageClass, mounts at /data, receives timestamp writes, and is later expanded to 8Gi.

How Effective Platform Engineering covers it

How deep it goes
Demonstrates manifests and executable checks but stops short of explaining claim-binding internals.
Examples
Uses EBS ReadWriteOnce and EFS ReadWriteMany claims with mounted pods, timestamp files, Bats checks, and capacity expansion.
What it assumes
Assumes Kubernetes, EKS, pods, StorageClasses, CSI drivers, and kubectl while illustrating claim testing through fixtures.
What you can do after
Diagnose storage integration by verifying binding, pod health, write access, shared writes, and claim expansion.
How it connects
Connects PersistentVolume, StorageClass, Pod, access modes, dynamic provisioning, volume expansion, node affinity, and tolerations.

Also explained in

Compare how 9 books explain persistent volume claim →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.