A Kubernetes cluster may be made up by 100+ nodes. At any given time, Kubernetes will automatically move containers around a cluster to ensure the containerized applications have the compute, memory, and storage resources it needs as workloads evolve and change. Therefore, containers are constantly being killed off, migrated, and spun up based on workload requirements. DevOps teams also often move Kubernetes environments between clusters, both on premises and in public clouds, as containerized applications are created, tested, and brought into production. 

As containerization technology evolved and began supporting traditional applications, the need arose to store the data created by the containerized application. The state of the application, which includes configurations and the session IDs, also needs to be stored so that upon restore it can continue running as previously.