Intro: SIG Cloud Provider
summary
SIG Cloud Provider forms to pull cloud-specific code out of the Kubernetes core, builds the Cloud Controller Manager and a focused cloud provider extraction subproject to move in-tree providers like AWS GCP VMware OpenStack into separate repos, and measures a ~30 MB per binary savings by removing provider dependencies. The goal is independent release cycles, smaller binaries and faster fixes; work includes staging-to-publish tooling, API abstraction design, and migration plans, but migration is slow due to dependencies, tech debt and production compatibility challenges.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:25Agenda
- 4:44cloud-controller-manager (CCM)
- 5:30Building CCM was not Enough
- 6:22Why out-of-tree?
- 10:04Cloud Provider Extraction Subproject
- 15:33LTS Working Groups
- 16:47Cloud Providers as Subprojects
- 17:55New Cloud Providers in Kubernetes
- 20:43Deep Dive: SIG Cloud Provider








