Defining SAP BTP Service Management in the Kyma Environment

Within the Kyma environment, Service Management allows you to connect SAP BTP services to your cluster and manage these by using the SAP BTP Operator module. The SAP BTP Operator module consists of different resources, required for the provisioning of third-party-services in Kubernetes clusters. These resources can be controllers, CustomResourceDefinitions, and others.

As stated above, when working within SAP BTP, Kyma runtime, you can use the SAP BTP Operator (which is based on the Kubernetes Operator pattern) with your Kubernetes cluster by utilizing Kubernetes-native tools. Through the SAP BTP Operator in your SAP BTP subaccount, you can consume and manage SAP BTP services that can be explored in the SAP Discovery Center.

Only subscribed services can be used in the respective SAP BTP subaccount and thus, only those can be used by Kyma runtime.

For the SAP BTP Operator module within the Kyma runtime, an Open Service Broker API (OSB API) allows for communication between the Service Broker and Service Manager. The SAP BTP Operator module in Kyma uses the Service Manager to manage and consume respective services on SAP BTP. The SAP BTP Operator module installs its API on Kubernetes through custom resources so that you can use Kubernetes-native tools to manage SAP BTP services through a Kubernetes API. The following illustration will give you a concise overview of this architecture:

How can you access Service Management with its Service Instances and Service Bindings on SAP BTP, Kyma runtime? You must follow the link to your Kyma dashboard from the SAP BTP cockpit, then navigate to Namespaces. You can create your own or choose an existing namespace. We recommend that you choose the default namespace. After entering a namespace, go to Service Management. There, you can create Service Instances and Service Bindings.