Volumes grow online and never shrink; StatefulSet template changes normally replace pods ordinal by ordinal; supported in-place pod resize is a separate path. The craft is expanding storage first, gating rolls with partition, and letting replication lag set the pace.
← Containers & Kubernetes / 58
mediumNewRazorpayPhonePeSnowflake
The database StatefulSet needs more CPU and larger volumes with no downtime. Walk me through volume expansion and the restart choreography.
Volumes grow online and never shrink; StatefulSet template changes normally replace pods ordinal by ordinal; supported in-place pod resize is a separate path. The craft is expanding storage first, gating rolls with partition, and letting replication lag set the pace.
Updated Sep 2026 · Grounded in researched DevOps, SRE and platform engineering interview loops, written to a senior-engineer editorial bar, and never padded to hit a word count.
20 answers per topic instead of 10, and your progress kept · no cardor unlock all 390 remaining answers · ₹2,000 / $25
UP NEXT ON YOUR JOURNEY
Next in this trackA service in the EU cluster must call one in the US cluster. What are the real options for cross-cluster service discovery?Next in this trackA pod requesting one GPU stays Pending on a cluster with idle GPU nodes. Debug it.Next in this trackYour job pods never complete because the mesh sidecar keeps running. What changed in Kubernetes to fix this?
DISCUSSION · 0
Nothing here yet. Say how you would answer it.