The DBA world has almost entirely rejected VMs, containers and even SANs for master databases, which never seem to quite work for production workloads. The iss

The DBA world has almost entirely rejected VMs, containers and even SANs for master databases, which never seem to quite work for production workloads. The issues are: 1) performance degradation - the DBA wants 100% of the possible hardware performance, not less, for masters 2) infrastructure updates affecting the database. k8s has had a lot of updates, which interfere with the average 400 days uptime achieved on physical hardware that I've seen 3) increasing query tail latency, measured at 3x or more under VMware for example 4) vendors disclaiming support (Oracle being the most notable example. They will only support their VM technologies per their license.) 5) sharing database infrastructure with anybody never turns out well. 6) stalls by adding yet another scheduler. Having said that, if you decide you just don't care about database performance, go ahead with what you feel is best. But don't whine about poor availability or queries being slow. Source: DBA who has worked with all of the above technologies. Just give me a pair of 2U servers with Fusion IO SSD cards!