Google launched a new framework that uses a pair of platforms to make it easier to connect a Kubernetes cluster to Google Cloud Platform (GCP) services. The move follows a similar launch by Microsoft last year.
The Kubernetes Service Catalog and the Google Cloud Platform Service Broker form the new superstructure. Together they help to connect to GCP services from a GCP-hosted Kubernetes cluster or an on-premises Kubernetes cluster.
The service catalog is installed into an existing Kubernetes or Google Kubernetes Engine (GKE) cluster. Once installed, the service catalog uses the service broker to provide access to GCP services. These include Google Cloud Storage, its BigQuery enterprise data warehouse, and Cloud SQL database manager.
It basically provides a direct connection between a running Kubernetes cluster and supporting services running outside of that cluster.
Both are based on the Kubernetes Catalog SIG and the Open Service Broker API. The former allows a developer to request services from a catalog without having to deal with provisioning. The SIG has also been working on integrating the Open Service Broker API with the Kubernetes ecosystem.
The Open Service Broker API was formed by the Cloud Foundry Project in late 2016 as an effort to create APIs for connecting applications to cloud-platform services. Founding members included Fujitsu, Google, IBM, Pivotal, Red Hat, and SAP.
Chris Crall, product manager at Google Cloud, said in a blog post that the combination allows developers to work in environments they are familiar with to create service instances and to connect those instances.
“With two commands you can create the service instance and set the security policy to give you application access to the resource,” Crall wrote. “You don’t need to know how to create or manage the services to use them in your application.”
Kubernetes began within Google as the Borg platform. Google spun off the platform into the open source community in 2015. The Kubernetes Project currently resides underneath the Cloud Native Computing Foundation (CNCF).
Microsoft Already Did It
Microsoft launched a similar platform last year with its Open Service Broker for Azure. It uses a specific implementation of the Open Service Broker API targeted at Azure services.
It provides similar features but is tied to various Azure cloud services. It can be run through Kubernetes, Cloud Foundry, OpenShift in Azure, Azure Stack, or on-premises.
https://www.sdxcentral.com
The Kubernetes Service Catalog and the Google Cloud Platform Service Broker form the new superstructure. Together they help to connect to GCP services from a GCP-hosted Kubernetes cluster or an on-premises Kubernetes cluster.
The service catalog is installed into an existing Kubernetes or Google Kubernetes Engine (GKE) cluster. Once installed, the service catalog uses the service broker to provide access to GCP services. These include Google Cloud Storage, its BigQuery enterprise data warehouse, and Cloud SQL database manager.
It basically provides a direct connection between a running Kubernetes cluster and supporting services running outside of that cluster.
Both are based on the Kubernetes Catalog SIG and the Open Service Broker API. The former allows a developer to request services from a catalog without having to deal with provisioning. The SIG has also been working on integrating the Open Service Broker API with the Kubernetes ecosystem.
The Open Service Broker API was formed by the Cloud Foundry Project in late 2016 as an effort to create APIs for connecting applications to cloud-platform services. Founding members included Fujitsu, Google, IBM, Pivotal, Red Hat, and SAP.
Chris Crall, product manager at Google Cloud, said in a blog post that the combination allows developers to work in environments they are familiar with to create service instances and to connect those instances.
“With two commands you can create the service instance and set the security policy to give you application access to the resource,” Crall wrote. “You don’t need to know how to create or manage the services to use them in your application.”
Kubernetes began within Google as the Borg platform. Google spun off the platform into the open source community in 2015. The Kubernetes Project currently resides underneath the Cloud Native Computing Foundation (CNCF).
Microsoft Already Did It
Microsoft launched a similar platform last year with its Open Service Broker for Azure. It uses a specific implementation of the Open Service Broker API targeted at Azure services.
It provides similar features but is tied to various Azure cloud services. It can be run through Kubernetes, Cloud Foundry, OpenShift in Azure, Azure Stack, or on-premises.
https://www.sdxcentral.com
No comments:
Post a Comment