Dualing Platforms: Building Services for Cloud Foundry and Kubernetes Using the Open Service Broker
summary
Open Service Broker API is a small, concrete spec that exposes three endpoints—catalog/provision/bind—so one broker can serve apps on Cloud Foundry env and Kubernetes cluster. Demo deploys a broker as a Cloud Foundry app, registers it with Cloud Foundry and Kubernetes Service Catalog, provisions instances, and creates bindings; Cloud Foundry receives credentials via injected environment variables, Kubernetes receives them as Secrets. Spec supports async provisioning and plan/config schemas so a single broker implements a service once and works across platforms.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:39Challenges in service delivery
- 3:58History of the broker API
- 5:25How the broker API works
- 8:35Cloud Foundry and Kubernetes
- 9:16Live demo of service binding
- 18:57Multi-cloud architecture
- 19:37Getting involved
- 20:34Q&A and conclusion
related talks
24mHow to Build Spring Services for Cloud-Native Platforms
36mAccessing Cloud Foundry Marketplace from your Kubernetes Cluster
32mThe Open Service Broker API and the Kubernetes Service Catalog
36mSIG Service-Catalog Intro – Doug Davis, Michael Kibbe & Morgan Bauer
36mPanel: Leveraging the Open Service Broker API in Cloud Native Platforms
30mSIG Service Catalog
34mConsuming cloud services with the Kubernetes Service Catalog
30mHow to Scale Single-Node Service Brokers with Subway