SIG Cluster Lifecycle: kubeadm Deep Dive
summary
kubeadm provides a repeatable bootstrap: install Docker and kubeadm packages, run kubeadm init / kubeadm join, then apply a CNI like weave-net and optional storage (example: Dotmesh) to get a 3-node cluster. Upgrades are improving but historically manual; work targets self-hosted control plane and a pilot light sentinel for reliable HA and easier upgrades, with dynamic component config planned in 1.11. Enterprise use covers pre-pull images, package choices, proxies, no-proxy ranges and configurable preflight checks for air‑gapped installs.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 7:45Corkscrew
- 8:32Selfhosting
- 16:55Alexander
- 17:28The Problem
- 18:05The Solution
- 21:08Version Labels
- 22:35Docker Images
- 23:43Network
- 24:35Container Runtime
- 24:53kubeadm
- 26:13Questions
related talks
41mDeep Dive: Cluster Lifecycle SIG (Kubeadm)
43mDeep Dive: SIG Cluster Lifecycle
46mSIG Cluster Lifecycle (Cluster API)
37mkubeadm deep dive (SIG Cluster Lifecycle)
37mkubeadm Cluster Creation Internals: From Self-Hosting to Upgradability and HA
38mIntro: SIG Cluster Lifecycle
40mIntro: Cluster Lifecycle SIG
41mSIG Cluster Lifecycle Intro
