在Kubernetes集群中，哪些主体能够创建Persistent Volume（PV）？

Hey there, let's break down Persistent Volumes (PV) and their counterpart PersistentVolumeClaims (PVC) in Kubernetes based on the official docs, in easy-to-understand terms:

Persistent Volume (PV) Basics #

• A Persistent Volume (PV) is a cluster-level storage resource configured by a Kubernetes admin. It's treated just like cluster nodes—part of the core infrastructure of your cluster.
• PVs act as volume plugins, similar to regular Kubernetes Volumes, but with a critical distinction: their lifecycle is independent of the individual Pods that use them. So even if the Pod that was using the PV gets deleted, the PV itself remains (unless its reclaim policy says otherwise).
• This API object holds all the specific details about the underlying storage system being used. Common examples include NFS, iSCSI, or cloud provider-specific storage like AWS EBS, Azure Disk, or GCP Persistent Disk.

What About PersistentVolumeClaims (PVC)? #

Since you're looking into PVs, it's hard not to mention PVCs—they're the user-facing side of persistent storage in Kubernetes. A PersistentVolumeClaim (PVC) is essentially a user's request for storage. Instead of dealing with the low-level storage details, users define their needs (like storage size, access modes) in a PVC, and Kubernetes automatically finds and binds it to a compatible PV that meets those requirements.

内容的提问来源于stack exchange，提问作者Anil Kumar P