Building a Controller Manager for Your Cloud Platform
summary
Cloud Controller Manager (CCM) is the Beta out‑of‑tree way to replace in‑tree cloud drivers and the goal is to move all providers out of core by end of 2019; build one by implementing the Go cloud provider interface, copying the CCM main, and shipping a separate binary container that runs as a DaemonSet or static pod. Testing requires unit tests plus e2e against a real cloud (OpenStack uses gophercloud and devstack, vSphere shares credentials with CSI), watch for the no-schedule taint and API rate‑limit chatty behavior.
AI-written summary · about
chapters (7)
- 0:00Start
- 9:06Introduction to Cloud Controller Manager
- 11:10Cloud Provider Interface
- 12:29Cloud Controller Binary
- 13:50Two Types of Testing
- 19:35Implementation Details
- 30:19SIG Cloud Provider
related talks
35mIntro: Cloud Provider SIG
35mSIG Cloud Provider Update
18mCloud Provider OpenStack Community Session
27mSIG Cloud Provider: Portable K8s Across all Clouds, Roadmap and Updates
32mSIG: Cloud Provider Moving Out of Tree+CSI - What it Mean...
35mBuilding a sovereign, vendor-agnostic Cloud API
38mSIG Cloud Provider Deep Dive: Testing Cloud Controller Managers
30mSIG Cloud Provider Intro
