Storage & Persistent Volumes Flashcards

Which field in a PersistentVolumeClaim spec determines how much storage is requested?

Answer: spec.resources.requests.storage

The spec.resources.requests.storage field in a PVC defines how much storage the claim requests from a PersistentVolume.

What happens to a PersistentVolume with Reclaim Policy 'Retain' when its PVC is deleted?

Answer: The PV moves to 'Released' status and data is preserved

With the Retain policy, deleting the PVC releases the PV (status becomes 'Released') but the data remains intact until an administrator manually reclaims it.

Which StorageClass parameter controls whether volumes can be expanded after creation?

Answer: allowVolumeExpansion

The allowVolumeExpansion field set to true in a StorageClass enables PVCs using that class to request more storage after initial provisioning.

A Pod mounts a PVC with ReadWriteOnce access mode. What does this allow?

Answer: Only one node can mount the volume in read/write mode

ReadWriteOnce (RWO) means the volume can be mounted as read-write by a single node at a time.

Which Kubernetes object is created automatically when dynamic provisioning is triggered by a PVC?

Answer: PersistentVolume

When a PVC references a StorageClass with a provisioner, Kubernetes dynamically creates a PersistentVolume object and binds it to the PVC.

What is the purpose of the 'volumeBindingMode: WaitForFirstConsumer' setting in a StorageClass?

Answer: It delays volume provisioning until a Pod using the PVC is scheduled

WaitForFirstConsumer delays volume binding and provisioning until a Pod using the PVC is actually scheduled, enabling topology-aware provisioning.

Which command shows the current status and binding information of all PersistentVolumes in a cluster?

Answer: kubectl get pv

kubectl get pv lists all PersistentVolumes cluster-wide, showing their capacity, access modes, reclaim policy, status, and bound claim.