Deep Dive: Cluster Lifecycle SIG (Kubeadm)
summary
Kubeadm now ships stable CLI and keeps control plane as static pods while adding concrete HA features: automatic certificate copy (upload-certs) encrypts CA material into a secret that expires after two hours, and node-specific TLS certs are generated at join time; joining additional control planes uses dynamic join --control-plane (experimental) and requires an external load balancer or careful etcd quorum handling. The project targets beta for the HA flow and kubeadm config v1beta2 in the next releases and preserves upgrade paths and token-based joins.
AI-written summary · about
chapters (26)
- 0:00Intro
- 0:28Who are we?
- 1:14What is kubeadm
- 2:07Kubeadm: key design takeaways
- 2:51Recent changes in kubeadm
- 3:04What does GA really mean?
- 4:06kubeadm configuration file
- 4:55kubeadm phases
- 6:10Kubeadm survey
- 6:44Deep dive: HA in kubeadm - part 1
- 7:29Certificates copy in a nutshell
- 9:22How it works @ init time
- 11:18Key takeaways!
- 12:45Deep dive: HA in kubeadm - part 2
- 13:36Why should you care?
- 14:13The external load balancer
- 15:36Stacked etcd
- 19:37Bonus pack
- 19:59The starting point
- 20:56The grand theory of HA in kubeadm
- 23:00History of HA in kubeadm
- 24:20Coming soon... 2019 roadmap
- 24:50The kubeadm roadmap
- 26:38How can you contribute
- 28:35Logistics
- 29:38Questions and Answers
related talks
43mDeep Dive: SIG Cluster Lifecycle
33mSIG Cluster Lifecycle: kubeadm Deep Dive
37mkubeadm deep dive (SIG Cluster Lifecycle)
37mkubeadm Cluster Creation Internals: From Self-Hosting to Upgradability and HA
38mIntro: SIG Cluster Lifecycle
32mIntro: SIG Cluster Lifecycle
35mIntro: SIG Cluster Lifecycle
46mSIG Cluster Lifecycle (Cluster API)