Around & After Kubernetes: The Principles and Ideas that Guide Us
summary
Company migrates infrastructure to Docker and Kubernetes, cuts server boot from two hours to ~three minutes, and commits to running apps on k8s while accepting early instability (they even run Elasticsearch on containers). They build an internal tool, Port Control, that automates workflows and exposes a REST API and has handled 58,000 deployments (3,900 last month), enables self-serve backups/restores, enforces SSO and automated revocation, and prioritizes reducing developer cognitive load, automation, shared ownership and incremental security improvements.
AI-written summary · about
chapters (15)
- 0:00Start
- 1:22Meet The Team
- 10:02Our Journey or Docker
- 19:38In Retrospect
- 21:00Halt The Proliferation of Tools
- 22:03Keep The Main Thing, The Main Thing
- 23:10The Cost of Abstractions
- 29:40Proactive Education
- 30:54Open Participation
- 32:29Security Is A Team Effort
- 34:09Security Is Not A Destination
- 35:48Empathy Underlies Our Processes
- 37:00Stuff We Need To Improve On
- 37:53In The Next Year
- 40:22In Summary ...
related talks
44mEvolving Dev and Ops with Kubernetes: Enterprise Adoption for Security, Speed, and Ease
20mKubernetes 101
38mBuilding the Perfect Infrastructure with Kubernetes
42mMastering Kubernetes: Challenges, Strategies, and Best Practices
14mLessons from the Kubernetes Adventure
29mFrom EC2 to Kubernetes Takeaways from a Brownfield Migration
44mMigrating a Monolith to Kubernetes
35mKubernetes journey