Tectonic Summit 2016: The Origins of Kubernetes
•Download as PPTX, PDF•
0 likes•366 views
Brendan Burns, one of the founders of Kubernetes, walks us through how Kubernetes came to be. 12/12/16
Report
Share
Tectonic Summit 2016: The Origins of Kubernetes
- 1. The origins of Kubernetes Brendan Burns Microsoft Azure Container Service
- 2. The origins of Kubernetes Brendan Burns Microsoft Azure Container Service 8
- 3. Pre-history 1979 - chroot 1982 - BSD 2000 - FreeBSD jail 2005 - Solaris Zones/Containers 2006-2007 - Linux CGroups and Namespaces 2006 - AWS begins selling VMs 2008 - I join Google websearch infrastructure teams
- 4. My Ops Experience Dev. and On-call for Google Web-Search No SSH No imperative configuration No room for errors
- 5. My Ops Experience Dev. and On-call for Google Web-Search No SSH No imperative configuration No room for errors
- 6. My Ops Experience Dev. and On-call for Google Web-Search No SSH No imperative configuration But lots of thoughts about Borg.
- 7. A starting point: Borg The merge of two systems: Global Work Queue Babysitter Lots of organic growth, spread out over time Utilization is the major problem to be solved
- 8. A step forward: Seattle 2012 WebSearch leaves Seattle :( But public cloud is growing :) But public cloud is using VMs :( But we can try to make it better :) Declarative configuration Server side deployment Health maintainance
- 9. The door flies open: Docker 2013 - Docker begins Image format and build tools Image distribution infrastructure Container runtime
- 10. The original idea: Seattle, Nov. 2013
- 11. A minimally viable, open source Docker orchestrator Only two challenges: func orchestrate(...) error { … }
- 12. The “minimally viable” borg: simplify ops O(N) = O(1)
- 13. The “minimally viable” borg: decouple all the things
- 14. The “minimally viable” borg: naming
- 15. The “minimally viable” borg: discovery
- 16. Lessons learned: Be consistent
- 17. Lessons learned: Everyone comes in the front door https://www.flickr.com/photos/16210667@N02/13504685914
- 18. Lessons learned: There is no hierarchy frontend bburns Node - 1 backend julia Node - 1 frontend julia Node - 2 backend bburns Node - 2
- 19. Lessons learned: There is no hierarchy frontend bburns Node - 1 backend julia Node - 1 frontend julia Node - 2 backend bburns Node - 2
- 20. Lessons learned: There is no hierarchy frontend bburns Node - 1 backend julia Node - 1 frontend julia Node - 2 backend bburns Node - 2
- 21. Lessons learned: There is no hierarchy frontend bburns Node - 1 backend julia Node - 1 frontend julia Node - 2 backend bburns Node - 2
- 22. Differences: It had to be public cloud
- 23. Differences: It had to be open
- 24. Differences: Build a community & ecosystem
- 25. Three years later Many, many clusters in production 40,000+ commits 1000+ contributors 191 Meetups around the world 3 extraordinarily humbled co-founders
- 26. Unsolved problems: Configuration App App App
- 27. Unsolved problems: Cloud development
- 28. Unsolved problems: Scaling our community
- 29. Thank You!