Kubernetes storage 101: Container storage basics
Summary
Use of containerised applications, usually with a container orchestrator such as Kubernetes, is currently a huge trend in IT, and is becoming almost ubiquitous with users across all sectors. For this reason, containers are well-suited to workloads that see massive spikes in demand, especially on the web, and mainly where Kubernetes’s automation functionality allows this to take place rapidly. It is storage that is written into the container and created from temporary scratch space on the host machine that exists for the lifespan of the Kubernetes pod. PVCs are defined in the pod’s YAML so that the claim travels with it and can be pretty simple, specifying just capacity and tier of storage, for example. There is provision for multiple cloned pods in Kubernetes, called a deployment, which share a single PVC, but this can lead to problems such as crashes.