Panel: Bringing The Cloud To Kubernetes - Moderated by: Nic Cope, Upbound
summary
Four cloud projects model provider APIs as Kubernetes resources: ACK, ASO, Config Connector and Crossplane. Teams build controllers and providers (ACK and Crossplane share a code-generation pipeline), aim to generate controllers from OpenAPI/ARM to fix the scaling/consistency problem, and ship concrete pieces like a vsphere provider released. Crossplane exposes cluster-scoped managed resources plus composition and a package manager for reusable configurations and functions; users report Config Connector running in production and developers lament things like 19 API calls to update a bucket.
AI-written summary · about
chapters (15)
- 0:00Panel introduction
- 1:04Cloud operator names
- 3:31Google Config Connector origins
- 5:38Azure Service Operator origins
- 6:41AWS Controllers background
- 8:09Crossplane mission
- 11:38Crossplane cloud APIs
- 14:29Separation of concerns
- 16:14Config Connector users
- 18:25High-fidelity cloud resources
- 22:15ACK and abstractions
- 25:08Building cloud operators
- 28:02Cloud API consistency
- 30:30Kubernetes Resource Model appeal
- 33:17Project teams' excitement
related talks
33mPanel: Kubernetes, Cloud Native and the Public Cloud [B]
30mPanel: Cloud Foundry and Kubernetes - The Blending Continues
23mIntroduction to Crossplane and Simplifying Cloud Native Infrastructure Management
40mKubernetes is Your Cloud Control Plane
35mPlays Well with Others: Composability for Cloud Native Applications
17mCrossplane: Deploy Your Cloud Components from Your K8S Cluster
36mCrossplane Intro And Deep Dive - The Cloud Native Control Plane Framework
33mEliminating the Gap Between Development and Production with Kuber...