5 ms·

I think this glosses over the downsides of sharing a kernel. There are lots of edge cases where containers can interfere with each other by consuming kernel res

I think this glosses over the downsides of sharing a kernel. There are lots of edge cases where containers can interfere with each other by consuming kernel resources or causing contention in certain kernel code paths. So you can run a db on kube ok, but a "production like" setup will be keeping other workload off the same kernel. So the kube bit is because it's what you prefer to operate, and you might as well be using vms.

lrvick 4y ago
You just simply pin the DB on dedicated workers. No big deal.
motoboi 4y ago
Create a scalable node pool just for databases. Each node with the right amount of memory (125% of what the a database instance will use) and CPU (db + 1 for kubernetes' infra). Taint the node pool so that only the database can tolerate it. Presto. Now when you scale up N instances, N new nodes are created.