Comment by dijit

the irony here of course is that Kubernetes is sort of designed to be run on bare-metal.

As a life-long ops person, a lot of the capabilities of kubernetes were things we used to bolt-on. (Like logging a boot ID so that we could track looks easier, service managing, having as little local state as possible so that the workloads are somewhat immutable and nodes can be cycled out, draining machines due to hardware failure (or cordoning them at least) etc;etc;etc)

Cloud came in and made some of those things a little easier I guess, but the value of kubernetes for most people is that they don't have to care about it because the providers give you a one size fits all solution: just don't peek under the hood.

Even the best implementation of Kubernetes (GKE) has a huge amount of waste due to software that has been added to every node and configured wrong.