![what is kubernetes pvc what is kubernetes pvc](https://jelastic.com/blog/wp-content/uploads/2019/07/kubernetes-cluster.png)
![what is kubernetes pvc what is kubernetes pvc](http://press.demo.kuboard.cn/assets/img/image-20191016151308410.375b744e.png)
Also, if there are one/more available/unbound PVs, then administrators can use this test to verify the configuration - i.e., the access mode and storage capacity - of such PVs. This way, administrators can figure out if the bind/relcamation status of a PV is why it could not be bound to a PVC. This test auto-discovers PVs and reports the bind status of each PV, thereby pointing administrators to those PVs that are unbound, bound, or released, and those that could not be reclaimed. If there are many unfulfilled PVCs, an administrator may quickly want to check the status of the existing PVs to determine why they could not be bound to any of the PVCs - is it because the PVs are already bound? is it because the PVs have been released, but cannot be reclaimed? or has reclamation failed for many PVs? The Kube Persistent Volumes test provides answers to these questions!
![what is kubernetes pvc what is kubernetes pvc](https://i.ytimg.com/vi/PCrOf5mbh4Q/maxresdefault.jpg)
When a user is done with their volume, they can delete the PVC objects from the API which allows reclamation of the resource. The PVC can be bound when a 100Gi PV is added to the cluster. For example, a cluster provisioned with many 50Gi PVs would not match a PVC requesting 100Gi. Claims will be bound as matching volumes become available. Claims will remain unbound indefinitely if a matching volume does not exist.
![what is kubernetes pvc what is kubernetes pvc](https://blog.kasten.io/hs-fs/hubfs/Partner%20Images/HPE/hpe-csi-volume-snapshot-kasten-k10.png)
If a PV was dynamically provisioned for a new PVC, the loop will always bind that PV to the PVC. When none of the static PVs the administrator created matches a user’s PVC, the cluster may try to dynamically provision a volume specially for the PVC. A control loop in the master watches for new PVCs, checks if any static PV (a PV manually created by the administrator) matches the new PVC, and binds them together. Typically, a user creates a PersistentVolumeClaim with a specific amount of storage requested and with certain access modes. Claims can request specific size and access modes (e.g., can be mounted once read/write or many times read-only). Pods can request specific levels of resources (CPU and Memory). Pods consume node resources and PVCs consume PV resources. PVs are volume plugins like Volumes, but have a lifecycle independent of any individual pod that uses the PV.Ī PersistentVolumeClaim (PVC) is a request for storage by a user. It is a resource in the cluster just like a node is a cluster resource. A PersistentVolume (PV) is a piece of storage in the cluster that has been provisioned by an administrator or dynamically provisioned using Storage Classes.