If they're expressing surprise at being able to run stateful applications, developing complex new patterns, and dispensing multiple iterations of experimental f

If they're expressing surprise at being able to run stateful applications, developing complex new patterns, and dispensing multiple iterations of experimental features to provide for this featureset, doesn't that show that it wasn't designed for it? >But your previous comment implied that Kubernetes was designed inherently for stateless tasks only. I would argue that there are things that make conventional databases an inherently bad fit for containerization, but I didn't say k8s was designed specifically to preclude the possibility of ever running any type of stateful app.