Shulou(Shulou.com)06/01 Report--

This article is about how to understand PV and PVC, the editor thinks it is very practical, so I share it with you to learn. I hope you can get something after reading this article.

Volume provides a very good data persistence solution, but there are still deficiencies in manageability.

Taking the previous example of AWS EBS, to use Volume,Pod, you must know the following information in advance:

The current Volume is from AWS EBS.

The EBS Volume has been created ahead of time and knows the exact volume-id.

Pod is usually maintained by the application developer, while Volume is usually maintained by the storage system administrator. Developers need to get the above information:

Or ask the administrator.

Or you are the administrator yourself.

This creates a management problem: the responsibilities of application developers and system administrators are coupled. It is acceptable if the system is small or for a development environment. However, when the size of the cluster becomes larger, especially for the generation environment, considering efficiency and security, this has become a problem that must be solved.

The solutions given by Kubernetes are PersistentVolume and PersistentVolumeClaim.

PersistentVolume (PV) is a piece of storage space in an external storage system that is created and maintained by an administrator. Like Volume, PV is persistent and its life cycle is independent of Pod.

PersistentVolumeClaim (PVC) is an application for PV (Claim). PVC is usually created and maintained by ordinary users. When you need to allocate storage resources for Pod, users can create a PVC that indicates the capacity of the storage resources and information such as access mode (such as read-only). Kubernetes will find and provide PV that meets the criteria.

With PersistentVolumeClaim, users only need to tell Kubernetes what kind of storage resources they need, regardless of the underlying details such as where the real space is allocated and how to access it. The underlying information of the Storage Provider is left to the administrator, and only the administrator should care about the details of creating the PersistentVolume.

Kubernetes supports many types of PersistentVolume, such as AWS EBS, Ceph, NFS, and so on.

The above is how to understand PV and PVC. The editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.