Kubernetes is awesome – but …
summary
Asks three concrete readiness questions: do I need Kubernetes?, does my workload fit (stateless, 12‑factor, scales per request), and do I have the manpower to operate it. Points to Azure + managed services, cert‑manager, ingress controller, PodDisruptionBudget and probes as decisive pieces. Gives failure examples: upgrade path from 1.19 to 1.23 breaks because ingress class annotations change and cert‑manager HTTP challenge broke after upgrade, and advises using managed databases, OPA/Kyverno policies, no‑root images and basic runtime alerts.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:28Background
- 2:24Kubernetes mission
- 4:06Pros
- 6:18Complexity
- 7:58Flexibility
- 9:30Three important questions
- 17:55Developer awareness
- 20:49Technical pitfalls
- 23:19Persistent storage
- 25:38Monolithic applications
- 29:01Pot disruption budget
- 30:36Has probes
- 37:02Wrap up
- 38:26Outro
related talks
54mKubernetes for the konfused, a strategy toolkit for normals
47mDo We Really Need Kubernetes? A Tactical Guide to Cloud Native
59mKubernetes - going beyond the basics
45mKubernetes Resiliency
36mHow to make Kubernetes rhyme with prod readiness - Tiffany Jernigan and Matthias Haeussler
04mKubernetes Hype - Do you really need it?
08mSponsored Keynote: Free Range Kubernetes: Feeding, Watering & Herding - Brian Goodman-Jones
51mKubernetes for the Impatient