Lightning Talk: Self-Service Provisioning with the Crossplane Service Broker- Tobias Brunner, VSHN
summary
Crossplane Service Broker translates the Open Service Broker API to Crossplane primitives, maps service offering to composite resource definition, maps plans to Compositions and instances to CompositeResources. A control cluster runs Crossplane and the broker, a service cluster hosts Helm-deployed services, and a consumer cluster uses the Kubernetes Service Catalog to request services. Demo provisions a Redis instance: broker creates a CompositeResource, Crossplane instantiates a Helm release on the service cluster, and a binding writes a secret with connection details on the consumer. Open source, production-used, roadmap: bearer-token auth, async binding, plan upgrades.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:10About VSHN
- 0:50Swisscom
- 1:54Open Service Broker API
- 2:48Live Demo
- 3:42Demo
- 7:22Roadmap
related talks
24mBeyond Infra/Service Provision: The Crossplane Essentials and Adoption
37mPlatformOps with Crossplane
23mIntroduction to Crossplane and Simplifying Cloud Native Infrastructure Management
30mGetting to Know Crossplane
24mDualing Platforms: Building Services for Cloud Foundry and Kubernetes Using the Open Service Broker
36mBreak the silo: How we built a decentralized control plane for service orchestration
33mEliminating the Gap Between Development and Production with Kuber...
31mCrossplane Intro and Deep Dive - The Cloud Native Control Plane Framework