SIG Cloud Provider Deep Dive
Talkat KubeCon + CloudNativeCon North America 2019 · on Wednesday, 2019-11-20· at 16:25· Pacific Ballroom, Salon 25-26 - Marriott Marquis San Diego Marina Hotel·
summary
SIG Cloud Provider explains how cloud code leaves the Kubernetes tree and what actually gets built to migrate safely: cloud controller managers move controllers out, a leader election lock prevents duplicate controllers during rolling upgrades (proof‑of‑concept works), in‑tree PVs migrate to CSI with a staged switch and snapshot/restore support, a reference connectivity server + daemonset agents (gRPC mTLS) solves API reachability, Cluster API adapters map machines to infra, and the community targets 1.21 as an aspirational removal date.
AI-written summary · about
chapters (23)
- 0:00Intro
- 0:59When
- 1:40Background
- 6:02Node IPAM Controller
- 6:55Service Route Controllers
- 9:58Cloud Controller Manager Migration
- 11:47Removing persistent volumes
- 15:48No rollback
- 16:16Provider specific networking
- 18:56Native IPS
- 19:31Erosion
- 19:59Other variants
- 21:26KMS
- 23:20Cluster API
- 24:29What is Cluster API
- 25:06Architecture of Cluster API
- 29:54How does it work
- 32:44What is Kubernetes
- 35:48Current version of CCM
- 38:42Deprecation message
- 39:05Publish date
- 40:43Integration points
- 41:13Wrap up
related talks
22mDeep Dive: SIG Cloud Provider
35mIntro: SIG Cloud Provider
38mSIG Cloud Provider Deep Dive: Testing Cloud Controller Managers
35mIntro: Cloud Provider SIG
01h 13mIntro + Deep Dive: Cloud-Provider SIG
27mSIG Cloud Provider: Portable K8s Across all Clouds, Roadmap and Updates
35mIntro: Cloud Provider SIG
36mKubernetes SIG Storage Deep Dive