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

This article is about how to understand the external Storage Provider, 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.

External Storage Provider

If Kubernetes is deployed on public clouds such as AWS, GCE, Azure, etc., you can directly use cloud disk as Volume. Here is an example of AWS Elastic Block Store:

To use ESB volume in Pod, you must first create it in AWS and then reference it through volume-id. For more information on how to use other cloud disks, please refer to the official documents of various public cloud vendors.

Kubernetes Volume can also use mainstream distributed storage, such as Ceph, GlusterFS, etc. Here is an example of Ceph:

The / some/path/in/side/cephfs directory of the Ceph file system is mount to the container path / test-ceph.

Compared to emptyDir and hostPath, the most important feature of these Volume types is that they do not rely on Kubernetes. The underlying infrastructure of Volume is managed by independent storage systems and is separate from the Kubernetes cluster. After the data is persisted, even if the entire Kubernetes crashes, it will not be compromised.

Of course, a storage system like operation and maintenance is not usually a simple task, especially when there are high requirements for reliability, high availability and scalability.

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

The above is how to understand the external Storage Provider, 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.