Multi-Cloud Kubernetes using Open Service Broker API & Kubernetes Service Catalog

Simply said, a multi-cloud strategy is the use of two or more cloud computing services. With such strategy users can choose the best services from different cloud platforms and combine them to create the best possible solution for your business. The 2018 State of the Cloud Survey shows that 81% of enterprises use multiple clouds.

Kubernetes has been widely accepted as the best way to deploy and operate containerized applications. And, one of the key value propositions of Kubernetes is that it can help normalize capabilities across cloud providers. What if a user wants to tie resources on different platforms to Kubernetes applications which will provide him with abundant advantage while not building the same on-prem? what platform do you put where to get the most value out of it in the most efficient way? Azure MysQL Service for MySQL or Amazon RDS for PostgreSQL? AWS SQS or Azure’s AQS? or Want to experiment with voice interfaces? Lex answers the call. You have 18 AWS services to choose from!

The Open Service Broker API is an industry-wide effort to meet the demand of consuming cloud services through a simple and secure mechanism. The project has contributors from Google, IBM, Pivotal, Red Hat, SAP and many other leading cloud companies.

Service Catalog and Service Broker

The Service Catalog provides a way for developers, ISVs, and SaaS vendors to provision instances of services that can be consumed by applications in a standard way. Service Catalog is an extension API that enables applications running in Kubernetes clusters to easily use externally managed software offerings, such as a datastore service offered by a cloud provider. A Service Broker is an implementation of the open-source Open Service Broker (OSB) API which simplifies the delivery of cloud-platform specific services to applications that run on Kubernetes.