How Does Google Release Kubernetes in GKE
summary
GKE describes a versioned bundle that upgrades more than 50 master components plus node OS and kubelet, ships over a four-day staged rollout, and supports three active minor channels (n, n+1, n+2) with short-lived patches. It introduces a lightweight packaging project called cluster bundle for component-based releases, publicizes geographic rollout and deprecation schedules, and adds risk controls like release channels, node surge upgrade (create then drain) and canary clusters; many features are open sourced.
AI-written summary · about
chapters (25)
- 0:00Intro
- 1:44Google Kubernetes Engine Overview
- 2:21After Cluster Creation
- 2:49Master Components
- 3:09Node Components
- 3:34Open Source to Google
- 4:02What's in a Version?
- 4:39A Timeline of Kubernetes Releases 2015-2019
- 6:34Themes impacting release strategy
- 9:23Prod Rollout
- 9:40Cluster Version
- 10:23Upgrading a Master
- 10:37Upgrading a Node
- 12:10Upgrade Schedule: Masters
- 12:32Version Lifecycle: Patches
- 13:43Enter: Component Based Releases
- 14:17Components A Flexible Packaging Solution
- 14:44Components Everything is a kubemetes Resource
- 15:13Release Lifecycle: Revisited
- 17:36Release Channels
- 18:51Release Notes
- 19:36Node Auto Upgrades
- 20:04Node Surge Upgrade
- 21:08Maintenance Windows
- 22:18Canary Clusters
related talks
41mKubernetes in Action: Examples from Google Container Engine
39mHow Google Cloud Hosts and Manages Kubernetes at Scale
22mKeynote: Kubernetes Project Update
22mKeynote: Backstage with Kubernetes
18mKubernetes Project Update
07mKeynote: High Performance Computing on Google Kubernetes Engine
51mKubernetes: Changing the Way That we Think and Talk About Computing
44mContainers and CI/CD on Google Cloud