The Path to Kubernetes Adoption Is (Not Just) Installing Kubernetes
summary
Kubernetes adoption requires organizational and architectural changes beyond just installing clusters: shift from ITIL to DevOps practices, define enterprise architecture choices (data models, supported languages and OS), and run a program to refactor monoliths into fast‑starting, recoverable microservices. The talk discusses using OpenShift, GitOps and CI/CD, and automation tools like Ansible or Salt, and warns that naive lift‑and‑shift cloud migrations can greatly increase costs (e.g., 50→200%).
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:06Speaker background
- 2:08Kubernetes limitations
- 3:58ITIL vs DevOps
- 5:46Cultural barriers
- 8:17Enterprise architecture
- 10:03Kubernetes purpose
- 12:35Monoliths vs microservices
- 15:05Pre-adoption checklist
- 16:53Adoption tips
related talks
33mKubernetes: Crossing the Chasm
35mNavigating the Kubernetes Odyssey: Lessons from Early Adoption and Sustained...
06mLightning Talk - When Kubernetes is Not the Solution
45mKube Me This! Kubernetes Ideas and Best Practices
35mKubernetes journey
14mLessons from the Kubernetes Adventure
35mKubernetes vs Reality
45mHow K8S Changed the World of Ops
