The idea behind persistent volumes is quite easy; the application can reserve some space for specific tasks and mark them as persistent volumes. When the application that is using this space terminates, the newly spawned application will get access to the data created by the previously-terminated application so they can restore the data. We can have a shared filesystem or we can have persistent volumes, as these are the only two ways to handle the problem.
Here, we will use EBS persistent volumes in AWS to understand how our data will be persisted on the EBS volume using the REX-Ray volume driver. The following procedure illustrates the problem of why we need persistent volumes:
- We will run the Redis Docker image ...
