DevOpsInterviewPrep logo
← Containers & Kubernetes / 44
easyNewFlipkartPhonePeRazorpay

Your app runs database migrations in an init container on every deploy. Defend or attack that pattern.

The gating instinct is right and the cardinality is wrong: init containers make every new replica race the same migration. Here is the once-per-release shape interviewers want, plus the rollback rule that shapes all DDL review.

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.

The gating instinct is right and the cardinality is wrong: init containers make every new replica race the same migration. Here is the once-per-release shape interviewers want, plus the rollback rule that shapes all DDL review.

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 trackOff-peak, the autoscaler removes nodes and our Spark driver got evicted mid-run. How does scale-down choose its victims?Next in this trackWorker nodes slowly fill their disks until DiskPressure appears. How does the kubelet decide what to clean up?Next in this trackWith tens of thousands of services, DNS lookups start timing out for five seconds at a stretch. Diagnose and fix Kubernetes DNS at scale.
DISCUSSION · 0

Nothing here yet. Say how you would answer it.