Kubernetes does not innovate in the Area of Storage. In fact it does not even adopt any interesting concepts from HPC. Each database container is attached to a

Kubernetes does not innovate in the Area of Storage. In fact it does not even adopt any interesting concepts from HPC. Each database container is attached to a single disk volume and they are not fungible. There are ways of moving beyong this model, but you have to innovate at the API layer. For example Microsoft Service Fabric, has reliable collections and queues. Its a single Dictionary and queue accessible by your application that is partitioned and replicated with your application. It scales with your application and always writes to local disk. Why I am unsure of merits of this implementation, I imagine we need something like that to trully have good approach to databases in the new paradigme https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-work-with-reliable-collections https://learn.microsoft.com/en-us/azure/service-fabric/servi...