Why Kubernetes? (Which Kubernetes?)
summary
Argues Kubernetes is best seen not as a product but as a customizable framework requiring engineering to encode policy standards, not just a stateless runtime, and that enterprises should prefer customized frameworks over quick open options like cops cube AWS because those assume policies and incur high change cost. Claims policy driven scheduling removes manual capacity planning, pushes SRE practices, and reports that lightning session pacing hit six rapid demos so expect pragmatic tradeoffs and platform work rather than magic.
AI-written summary · about
related talks
52mKubernetes isn't the answer
11mKeynote: Stitching Things Together
24mYou probably don't need K8S
44mQ&A
40mThe Elephant in the Kubernetes Room: Team Interactions
21mKeynote: In Search of the Kubernetes "Rails" Moment
47mDo We Really Need Kubernetes? A Tactical Guide to Cloud Native
26mKeynote: Kubernetes - The Universal Control Plane