Are You Vmweary?
summary
Argues that many Kubernetes deployments still run on VMs out of habit, adding 20–30% performance overhead and extra software layers, and recommends evaluating tenant needs instead of defaulting to dedicated clusters. Cites Aussie Broadband moving from VMs to bare metal and eliminating 195 virtual machines, nearly a thousand CPU cores and a terabyte of RAM. Describes the tenancy spectrum from namespaces to separate clusters and highlights vCluster control plane in a pod as a way to get cluster-level isolation on shared bare metal.
AI-written summary · about
chapters (8)
- 0:00Introduction and purpose
- 1:48Factory evolution and inefficiency
- 3:56Virtualization history and hypervisors
- 6:27Containers and Kubernetes emergence
- 8:57Why virtual machines persist today
- 11:50Cost and performance overhead of VMs
- 13:15Tenancy solutions in Kubernetes
- 14:19Summary and call to action
related talks
38mKubernetes on Bare-Metals or VMs? Or Using Virtink to Have Pros of Both?
23mVirtual Kubernetes Clusters: A New Approach to Multi-tenancy
37mTenant Autonomy & Isolation In Multi-Tenant Kubernetes Clusters - A Comprehensive Guide
54mKubernetes VM Solutions for Multi-Tennant Applications
14mFrom cloud to bare metal with Kubernetes, a bad idea?
43mBuilding Monetary Confidence in the Cloud
40mMulti-tenancy in Kubernetes
35mMulti-Tenancy on Kubernetes with Virtual Clusters