Bare-Metal or Virtualized #Kubernetes? ๐Ÿค”

How do you use Kubernetes? Bare-Metal, Virtualized, Fully Managed? ๐Ÿงต๐Ÿ‘‡

Our CEO @robpankow has a clear opinion. There is no good reason to run Kubernetes virtualized. Unless you want to waste worthwhile hardware resources that is.

Containerization is a thin layer baked into the operating system, typically Linux, to isolate processes into their own namespaces, nothing else.

See the difference for yourself!
https://sblk.xyz/bare-metal-k8s

Bare-Metal Kubernetes: Power of Direct Hardware Access

Experience the performance boost of running Kubernetes on bare metal. Improve access to hardware resources and increase storage performance.

simplyblock
@simplyblock @robpankow That's quite a nonsense picture. Kubernetes is never a layer under your container. There is no OS in your container. There are good reasons to run Kubernetes on VMs since you might want to isolate workloads using virtualisation allowing different scaling models.

@sheogorath @robpankow good catch, the OS over Kubernetes was supposed to be container. Seems our designer missed the small difference (as did I). I'll fix it.

On the different scaling models, would you mind explain what you mean?

@simplyblock @robpankow A simple example would be: More Kubernetes clusters than you have physical hosts. Or different storage sharding for image caching, better isolation for untrusted workloads, โ€ฆ

Al lot of that can be done with kube-virt, but kube-virt isn't best in class in all these things.

There are micro-VM setups like firecracker or kata-containers, but finding experts in these is harder.

Kubernetes is amazing but not always the solution ;)