Intro: Cloud Provider SIG
summary
Kubernetes is extracting in-tree cloud providers to out-of-tree modules with a goal of removing entry providers by end of 2019 and moving deprecated code into staging, so vendors must implement the CloudProvider interface and publish a separate binary. Cloud-specific controllers (node, route, service, load‑balancer) run in a cloud controller manager daemonset with --cloud-provider=external and a cloudprovider.kubernetes.io/uninitialized taint; expect CSI storage migration caveats, end-to-end tests reported to TestGrid, and potential cloud API rate‑limit issues.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:50Agenda
- 2:39Background
- 3:42Origin Story
- 4:22Issues
- 6:15Cloud Providers
- 8:50Cloud Controller Manager
- 13:49Building Your Own Cloud Provider
- 15:03Cloud Provider Interfaces
- 16:05Cloud Provider Code
- 16:34Cloud Controller Binary
- 19:48Running Cloud Provider
- 21:09Behavioral Changes
- 23:30Implementation Details
- 24:21How to get involved
