Skip to main content

Storage for Kubernetess

Kubernetes storage provides data that outlives a single container or Pod. PersistentVolumes represent storage in the cluster, PersistentVolumeClaims request it, and StorageClasses provision it dynamically. StatefulSets use these to run stateful applications such as databases with stable identities and per-Pod volumes.

Stage: Configuration and Storage · Part of the Kubernetes roadmap · Last reviewed 19 November 2026

What to learn in Storage

Storage interview questions

Why use a StatefulSet instead of a Deployment for a database?

A StatefulSet gives each Pod a stable name, such as db-0, an ordered start and stop sequence, and its own persistent volume that follows it across restarts. Deployment Pods are interchangeable and share identity, which does not suit clustered stateful software.

What is the relationship between a PV and a PVC?

A PersistentVolume is a piece of storage in the cluster, either provisioned by an administrator or dynamically. A PersistentVolumeClaim is a user request for size and access mode. Kubernetes binds a claim to a matching volume, and Pods reference the claim.

Where Storage fits in the Kubernetes roadmap

Storage belongs to the Configuration and Storage stage (advanced level), which takes about 22 hours. State and settings.

Back to the full Kubernetes roadmap