Q: You need to run a database in Kubernetes. Someone says just use a Deployment with a PVC. Is that okay?
Not ideal. A Deployment doesn't guarantee stable pod identity or ordered startup/shutdown, which matters for clustered databases (Postgres HA, MySQL replication, Cassandra).
Want to master this scenario in a live sandbox? KodeKloud's PostgreSQL Database Administration & High Availability Course covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "Kubernetes is a declarative desired state system; understanding the reconciliation loop is how you diagnose this quickly. The interviewer is testing: StatefulSet necessity understanding.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
Not ideal. A Deployment doesn't guarantee stable pod identity or ordered startup/shutdown, which matters for clustered databases (Postgres HA, MySQL replication, Cassandra). Also, if a Deployment has multiple replicas, all pods might try to bind the same PVC — which only one can do (unless using ReadWriteMany).
- Each replica gets its own PVC via
volumeClaimTemplates. - Pods get stable DNS names (e.g.,
mysql-0.mysql,mysql-1.mysql) needed for replication setup. - Ordered startup ensures primary starts before replicas.
Remediation & Permanent Safeguards
StatefulSet is the right choice because: For a single-instance DB with no replication, a Deployment + PVC works fine but is still a corner case.
- Each replica gets its own PVC via volumeClaimTemplates.
- Pods get stable DNS names (e.g., mysql-0.mysql, mysql-1.mysql) needed for replication setup.
- Ordered startup ensures primary starts before replicas.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Applying exclusive-lock DDL table migrations on live production databases during peak traffic windows when configuring need database Kubernetes DDL migrations that acquire an exclusive table lock block all concurrent queries, queuing connections until the database connection pool exhausts.
- Allowing high-frequency queries to trigger full table scans without appropriate composite indexing when configuring need database Kubernetes Sequential table scans saturate database CPU and disk I/O, evicting frequently queried data from the buffer cache and causing cascading timeouts.
- Disabling referential integrity constraints during bulk ETL imports without post-import consistency validation when configuring need database Kubernetes Skipping relational consistency checks risks introducing orphaned records and referential integrity violations into production tables.
- Relying on database snapshot backups that have never been verified through automated restoration drills when configuring need database Kubernetes Backups that have never been tested with automated restore verification frequently fail during real disaster recovery scenarios.