AWS & Kubernetes: The Definitive Guide to Data Persistence with PV and PVC

Key Takeaways

now we are going to see about persistent storage for kubernetes this is where persistent volume and persistent volume claim terminology are used let's get started when you see data persistence in kubernetes whenever an application runs and stores the data in the port it is not permanent as soon as the Pod get deleted the data gets deleted so how can we retain the data let's take an example MySQL data you are saving data to the database and you want those data to persist but when the bot get destroyed data gets destroyed so how can we solve this issue that's when this persistent volume comes let's see in this picture how the persistent volume and persistent volume claim works how can the Pod attain a storage that can be permanent firstly we need to create a storage in AWS it could be EFS or EBS EFS elastic file system generally used for multi-read multi-rut elastic Block store generally used for read write once which means one board can write only one but if it's EFS multi rights or multi-read that time a multiple ports can write the same time so we create either EFS or EBS in AWS then what is PV what is persistent volume persistent volume is something that to let kubernetes know there is a volume exist there in the cloud using persistent volume we inform kubernetes here is the volume using persistent volume claim the Pod request the persistent volume the way the Pod gets the volume is by submitting a request which is called persistent volume claim this is a quick overview now we are going to dive into the deep examples first step how we can create a elastic file store elastic file system in elastic file system just go to the dashboard and fill all those details at the end you will get a file system ID that's the first step second step is that in kubernetes you create a persistent volume in the persistent volume you mention the file system ID which we got on the previous step this is how you let kubernetes know that there is a volume exist there the third step is that you create a persistent volume claim using persistent volume claim the Pod requests or it binds to the persistent volume it claims the volume that it want to use if you see a Port you can clearly see that EFS claim you mentioned the name of the persistent volume claim there this is how everything is linked support links to a person volume claim which is EFS claim in the EFS claim is the name of the personal volume claim and this request is made to the person and the persistent volume will link back to the file system right this is how the link works this is the static provisioning but we want Dynamic what are the advantages of having a dynamic it helps us to Auto scale it helps us to reuse the storage so the way we can use the dynamic storage is that you need to define a storage class in this example we use storage class and same like the first step where we create the file system you will get the file system number as well you assign that to the storage class and you give a name to the storage class in this way whenever you want to claim for the persistent volume you can mention the storage class there in that way it's more Dynamic and you can request persistent volume claim multiple times to that file system if it is the static way you can claim only once to the file system but in this way you can claim multiple times multiple storage to the file system and the persistent volume claim can be multiple times assigned to the storage Clause report then links back to the persistent volume claim this is how everything is linked you can see EFS claim one and here also you can see efficient that's how everything is linked together so this is a quick overview of the different types of storage static provisioning and also Dynamic frame provisioning and the way the persistent volume claim on the personal volume Works in kubernetes thanks for watching