 What is a volume? Containers are a firmware by definition, which means that everything that is stored at runtime is lost when the container is stopped. How we can make that content persistent using Kubernetes volumes? There are four Kubernetes objects we need to be aware of, volume, a persistent volume, or an storage class, or a persistent volume plate. In my current Kubernetes cluster, I've got a storage class provided by my administrator. I'm going to keep cutoff, get a C, and you'll see that there is here a standard default storage class, which in this case is a provision of Google Cloud Engine. And as instead of default, if I do not specify the storage class in my other files, then this one that is taken. Now, let me show you, first of all, the persistent volume claim. I want to deploy an application and I need to request some space, and this is done with the persistent volume plane object, which has a name and the access mode, and also the amount of storage that I request. Then, this is the persistent volume claim, and then I need to set this persistent volume and this persistent volume claim into my application. So my application is aware of it. And as you can see here, I've got my pot deployment, which I set a volume amount in slash tmp slash demo. This is where all the content, all the persistent content is going to be stored from the point of view of the pot. And then in the volumes, what I'm setting is what is the claim that I want to use. And in this case, I want to use my boot volume claim, which is the one that I've defined here. So I've already have my application here up and running with the persistent volume and so on. And I'm going to do a kifcattle exec. I'm going to go inside the pot and I'm going to write something in the follow directory. If I go to slash tmp slash demo, this is the volume that I've defined it and see that there is no file here yet. So you can do a call localhost, 8080 slash append greetings. I'm reading file. I'm just created a new file called greeting.txt. And if I do a cat, I can see that it just says jumbo here. You can see this is the content of file. So now let me do an exit and then delete the pot. So now I'm just killing my boot demo pot. So if we were not using a volume, then the greeting.txt file will just remove it as well. But let's see what's happening now because I'm just using volumes and a persistent volume claim set to the default storage class. Let me do a kifcattle now, apply minus f of the, again to start the pot. Pot. Okay, this is my new pot that I'm creating right now. Let me wait until it's up and running. And now if I do an exec, notice that this is a fairly new pot, started 10 seconds ago. I can do a cat in a slash tmp slash demo slash greeting.txt. And you can see here that it is the jumbo because volumes when used with the distributed file system makes your content persistent. Thanks for watching. And don't forget to like the video and subscribe to the channel.