Are these conditions sufficient for Kubernetes to dynamically provision a persistentVolume, assuming there are no limitations on the amount and type of available external storage?

Are these conditions sufficient for Kubernetes to dynamically provision a persistentVolume, assuming there are no limitations on the amount and type of available external storage?

Solution: A default provisioner is specified, and subsequently a persistentVolumeClaim is created.
A . Yes
B . No

View Answer

Answer: B

Explanation:

= The conditions are not sufficient for Kubernetes to dynamically provision a persistentVolume, because they are missing a StorageClass object. A StorageClass object defines which provisioner should be used and what parameters should be passed to that provisioner when dynamic provisioning is invoked. A persistentVolumeClaim must specify the name of a StorageClass in its storageClassName field to request a dynamically provisioned persistentVolume. Without a StorageClass, Kubernetes cannot determine how to provision the storage for the claim.

Reference: Dynamic Volume Provisioning | Kubernetes

Persistent volumes and dynamic provisioning | Google Kubernetes Engine …

Dynamic Provisioning and Storage Classes in Kubernetes or Dynamic Provisioning and Storage Classes in Kubernetes