The old myth that "containers are only for stateless workloads" died years ago. Today, production Kubernetes environments routinely host mission-critical stateful workloads, from transactional databases and Kafka clusters to AI/ML feature stores and virtual machines.
When teams move stateful applications into production on Red Hat OpenShift on IBM Cloud, they quickly encounter a fundamental storage architecture decision: Should they use cloud-managed block volumes, or deploy in-cluster software-defined storage with OpenShift Data Foundation (ODF)?
Treating storage like an afterthought works fine until a database pod restarts on a new node and sits in CrashLoopBackOff while you explain to leadership what an attach-detach timeout is. As the product manager working on container storage at IBM Cloud, I walk engineering teams through this choice every week.…