Service Catalog All the Things
Show Overview: Brian and Tyler talk with Paul Morie (@cheddarmint, Principal Software Engineer @RedHat, Lead of Kubernetes Service Catalog SIG) about the evolution of the Open Service Broker API, integrating with external services, the role of Service Brokers, and use-cases to expand Kubernetes applications.
- Kubernetes Service Catalog SIG
- OpenShift Commons - Kubernetes Service Catalog Deep Dive
- Kubernetes Service Catalog SIG (meetings, demos)
- Open Service Broker API
Topic 1 - Welcome to the show. Before you got involved in the Service Catalog SIG, you worked on several other aspects of Kubernetes (security, etc.). Tell us about some of the things you’re been involved with?
Topic 2 - Let’s go back to when the Open Service Broker API was announced. What was the purpose and how did it evolve to where it is now?
Topic 3 - What are the basics of how the Service Broker / Service Catalog interacts with applications on Kubernetes and 3rd-party services?
- Example: How do we think about user/password/security credentials to a database?
- Example: Is the Service Broker in the data path as well as the control path?
- Example: Where would traffic auditing functions happen?
Topic 4 - We saw a demo of the Service Catalog/Broker at Red Hat summit during an announcement with AWS, where is showed AWS services as part of the catalog. Previously, we’ve seen the CF Service Broker interact with Google or Azure services. Is the relationship between the broker and cloud-services “cloud specific”, or will things be interchangeable at all?
Topic 5 - Beyond public cloud services, what other types of things might be interconnected or managed via the Service Broker?