The state of on-prem Kubernetes
summary
Built on eight years of on‑prem work and three months of backporting, the claim is that Kubernetes itself is easier than integrating it into a 15,000‑line Perl provisioning system. Tools compared: kubeadm over SSH (kubespray/ansible) for simple installs, cluster API requires another Kubernetes to bootstrap so your laptop or an admin cluster becomes critical, EKS‑Anywhere + Tinkerbell, Rancher/k3s, OpenShift, Talos/Omni. Trade‑offs: API vs SSH provisioning, lack of SSH on Talos, operational buy‑in, and utilization arguments like “only 40% CPU used” versus real packing gains.
AI-written summary · about
chapters (8)
- 0:00My first Kubernetes journey
- 5:21Defining pets vs. cattle
- 6:47Why run on-premises?
- 7:46Addressing environment constraints
- 26:01The Cluster API debate
- 26:59Tooling and operational reality
- 36:08Q&A session
- 41:08Final thoughts on backups
related talks
36mThe Road to More Usable Kubernetes
45mKubernetes Operability Tooling
43mKubernetes Operability Tooling
35mNavigating the Kubernetes Odyssey: Lessons from Early Adoption and Sustained...
42mKubernetes on-premises
21mDeploying Kubernetes at scale
35mKubernetes journey
24mWe Broke Free From Cloud-Managed Kubernetes...
