Open Service Broker API: Creating a Cross-Platform Standard
summary
Project moves the Open Service Broker API into a cross‑platform GitHub org and adds concrete extensions: profile fields to replace org/space IDs, a JSON Schema for broker-provided config so UIs can render options, new GET endpoints, relaxed auth with standardized OAuth2 scopes, identity propagation, backup/restore hooks and async bind/unbind. Kubernetes proof‑of‑concept is the Service Catalog using CRD-like resources (Broker, ServiceClass, Instance, Binding), secrets for credentials and a pod preset injector; current state is alpha and very near beta, and the integration is working end‑to‑end.
AI-written summary · about
chapters (7)
- 0:00Introduction and motivation
- 5:46Cross-platform API initiative
- 8:01Roadmap and upcoming features
- 13:09Kubernetes Service Catalog update
- 22:19Implementation challenges
- 25:07Status and next steps
- 26:33Q&A
related talks
32mThe Open Service Broker API and the Kubernetes Service Catalog
36mPanel: Leveraging the Open Service Broker API in Cloud Native Platforms
30mSIG Service Catalog
09mConversation with Sarah Novotny, Head of Open Source Strategy for GCP, Google
21mOpen Services Cloud: A New Open Model
14mThe Makers of Marvels
02mBringing Clarity to Complex Event Driven Architectures with Standardized API Language
30mOpen Services Cloud: Unleash the power of self-operated cloud managed services
