Introducing Service Broker for Kubernetes
We are pleased to announce the general availability of
Oracle Cloud Infrastructure Service Broker for Kubernetes. With the continued
adoption of DevOps and Kubernetes, developers want to streamline their
automated deployment strategies to include provisioning and binding to any
cloud service on which their application or microservice depends. For example,
if your application depends on object storage wherever the application is
running, then provisioning storage buckets should be part of the deployment process
for the application. Better yet, it should be part of the deployment process
within Kubernetes.
This notion of simplified and combined deployment is what
spawned the Open Service Broker API project, which provides a consistent model
for exposing cloud services to applications and application deployment tooling.
The new service broker is an implementation of the Open Service Broker API for
use in a Kubernetes cluster and for use with Oracle Cloud Infrastructure
services. It simplifies access to Oracle Cloud Infrastructure services,
including new services like our Autonomous Databases, which can be a highly
scalable, automated, self-tuning backend for microservices and containerized
applications.
OCI Service Broker Architecture
How Service Broker Works
Oracle Cloud Infrastructure Service Broker for Kubernetes is
available as a Helm chart, a Docker container, and in open source. It includes
service broker adapters for the following services (with more to come):
Autonomous Transaction Processing
Autonomous Data Warehouse
Object Storage
Streaming
You can add the service broker to your Kubernetes cluster,
and then use the Open Service Broker APIs from within kubectl to interact with
the preceding cloud services. You don't need to provision these services before
you deploy your application, or remember to clean them up after you un-deploy
the application.
Service brokers enable application portability, too. The
combination of a consistent model and embedding cloud service provisioning
within your application deployment process means that when you deploy your
application in a new cloud environment, it has everything that it needs to run.
This is true for dev-test-production progressions, and for on-premises-to-cloud
migrations.
To further enable application portability, a service broker
can also be used to create service bindings to cloud services. For each binding,
the service broker creates a Kubernetes secret that contains necessary
information to connect to the service. Contents and format vary. For example, a
binding to the Object Storage service can contain a pre-authenticated URI to
access the storage bucket.[Source]-https://blogs.oracle.com/cloud-infrastructure/introducing-service-broker-for-kubernetes
Basic
& Advanced Kubernetes Training using cloud computing, AWS, Docker etc. in Mumbai. Advanced
Containers Domain is used for 25 hours Kubernetes Training.
Comments
Post a Comment