Subject: SAP Kyma
SAP Kyma is a powerful platform for building and extending cloud-native applications in the SAP ecosystem. A key feature that enhances the flexibility and integration capabilities of Kyma is its support for Service Brokers. Service Brokers provide a standardized way to provision, manage, and consume services within the Kyma environment, making it easier to integrate SAP services, third-party APIs, and custom microservices.
This article delves into managing and configuring SAP Kyma’s Service Brokers, highlighting best practices and practical guidance for developers and administrators.
Service Brokers act as intermediaries that expose services to applications running within Kyma via the Open Service Broker API (OSBAPI). They allow Kyma applications to:
SAP Kyma leverages Service Brokers to seamlessly integrate services such as databases, messaging queues, SAP backend services, and cloud offerings.
Service Catalog
The Service Catalog is the central repository listing all available services exposed by brokers. Applications can browse this catalog to find services to consume.
Service Instances
When a service is provisioned, a service instance is created. This represents a provisioned and configured service tailored for a specific application or use case.
Service Bindings
Bindings provide the credentials and connection details that allow applications to securely access the provisioned service.
To make a service available within Kyma, you first need to register the service broker:
kubectl apply -f service-broker.yaml
This configuration defines the broker endpoint, authentication, and the services it exposes.
Once registered, list all services exposed via brokers:
kubectl get serviceclasses
This command shows the catalog of services that applications can provision.
To provision a new service instance, create a ServiceInstance custom resource:
apiVersion: servicecatalog.k8s.io/v1beta1
kind: ServiceInstance
metadata:
name: my-db-instance
spec:
clusterServiceClassExternalName: postgresql
clusterServicePlanExternalName: standard
parameters:
storageGB: 20
Apply the manifest:
kubectl apply -f service-instance.yaml
Create a ServiceBinding resource to bind your application to the service:
apiVersion: servicecatalog.k8s.io/v1beta1
kind: ServiceBinding
metadata:
name: my-db-binding
spec:
instanceRef:
name: my-db-instance
This generates the credentials and injects them into the application environment.
Configure secure authentication mechanisms such as Basic Auth, OAuth, or client certificates for your service brokers to protect service provisioning endpoints.
Ensure the service catalog is regularly synchronized with the broker to reflect updated service plans and metadata.
Plan for versioning and updates in service brokers to avoid disruptions. Kyma supports smooth upgrades by allowing multiple versions of service plans.
Service Brokers in SAP Kyma play a pivotal role in enabling dynamic, scalable, and secure service consumption within cloud-native applications. Proper management and configuration of service brokers unlock seamless integration with SAP services and external systems, empowering developers to build robust extensions and integrations.
By adopting best practices and leveraging Kyma’s tooling, organizations can maximize the value of their SAP Kyma deployments and accelerate innovation in their cloud-native journey.