stateful-workloads
Stateful Workloads
Kubernetes and most modern orchestration platforms were designed around the assumption that any instance can be killed and replaced without consequence. That assumption is exactly wrong for stateful systems — a database pod is not interchangeable with a fresh one, because the data lives on that one pod's storage and nowhere else until you've deliberately made it otherwise.
Running state on infrastructure built for stateless workloads works, but only if you actively undo the platform's default assumptions: give the workload stable identity, give it storage that outlives the pod, and give it a recovery story that does not depend on the pod ever coming back the way it left.
The platform will happily reschedule, evict, and recreate your stateful pod exactly like a stateless one — unless you've told it not to, in writing, ahead of time.