Thriving With Kubernetes On-Call: Best Practices & Lessons Learned
Talkat KubeCon + CloudNativeCon North America 2022 · on Thursday, 2022-10-27· at 14:30· Virtual Platform Only·
summary
Large-scale companies describe concrete practices: primary/secondary rotations (week-long or daily, Netflix-style versus three-day at others), three to six months of onboarding with shadowing and reverse-shadowing, and tooling like Prometheus + Grafana, OpenTelemetry, Elasticsearch/Kibana, plus CLI work (kubectl, kubectx) and SSH for escape hatches. They build productized abstractions (CRD archetypes, OneTouch-style APIs), a platform CD and Houston incident logs, and small self-healing controllers and canaries; these reduce pages and mostly work, but runbooks and metrics constantly need tuning.
AI-written summary · about
chapters (7)
- 0:00Kubernetes on-call basics
- 2:26Splitting team roles
- 8:29Escalation policies
- 10:13On-call knowledge sharing
- 16:28Training new on-call members
- 25:03Kubernetes troubleshooting tools
- 34:30Q&A
related talks
42mMastering Kubernetes: Challenges, Strategies, and Best Practices
40mFrom dev to prod. One Year of Using Kubernetes in Production
31mHow to Build a Healthy On-call Culture
36mHow to make Kubernetes rhyme with prod readiness - Tiffany Jernigan and Matthias Haeussler
50mYou build it, you run it (why developers should also be on call)
56mBest practices for optimizing Kubernetes applications on AWS
22mRaise a Production System:Making on-call human-scale w/ Observability & Trust
35mKubernetes journey