Use the SAP BTP Operator module to enable service management and consume SAP BTP services from your Kyma cluster.
The SAP BTP Operator module provides service management, which allows you to consume SAP BTP services from your Kyma cluster using Kubernetes-native tools. Within the SAP BTP Operator module, BTP Manager installs the SAP BTP service operator. The SAP BTP service operator enables provisioning and managing service instances and service bindings of SAP BTP services. Consequently, your Kubernetes-native applications can access and use the services from your cluster.
The SAP BTP Operator module provides the following features:
- Credentials and access preconfiguration: Your Secret is provided on Kyma runtime creation. See Preconfigured Credentials and Access.
- Multitenancy: You can configure multiple subaccounts in a single cluster. See Working with Multiple Subaccounts.
- Lifecycle management of service instances and service bindings: You can create and delete service instances and service bindings. See Create Service Instances and Service Bindings and Delete Service Bindings and Service Instances.
- Service binding rotation: You can enhance security by automatically rotating the credentials associated with your service bindings. See Rotating Service Bindings.
- Service binding Secret formatting: You can use different attributes in your ServiceBinding resource to generate different formats of your Secret resources. See Formatting Service Binding Secrets.
By default, the SAP BTP Operator module consumes SAP BTP services from the subaccount in which you created it. To consume the services from multiple subaccounts in a single Kyma cluster, configure a dedicated Secret for each additional subaccount.
The SAP BTP Operator module provides and retrieves the initial credentials that your application needs to use an SAP BTP service.
Depending on the number of configured Secrets, SAP BTP Operator can have access to multiple subaccounts within your cluster.
For more information on multitenancy, see Working with Multiple Subaccounts.
SAP BTP, Kyma runtime runs on a Kubernetes cluster and wraps the SAP BTP Operator module, API server, and one or more applications. The application or multiple applications are the actual consumers of SAP BTP services.
BTP Manager is an operator based on the Kubebuilder framework. It extends the Kubernetes API by providing the BtpOperator Custom Resource Definition (CRD). BTP Manager performs the following operations:
- Manages the lifecycle of the SAP BTP service operator, including provisioning of the latest version, updating, and deprovisioning.
- Configures the SAP BTP service operator.
The SAP BTP service operator is an open-source component that allows you to connect SAP BTP services to your cluster and manage them using Kubernetes-native tools. It is responsible for communicating with SAP Service Manager. The operator's resources (service instances and service bindings) come from the services.cloud.sap.com API group.
SAP Service Manager is the central registry for service brokers and platforms in SAP BTP, which enables you to:
- Consume platform services in any connected runtime environment.
- Track the creation and management of service instances.
- Share services and service instances between different runtimes.
SAP Service Manager uses Open Service Broker API (OSB API) to communicate with service brokers.
Service brokers manage the lifecycle of services. SAP Service Manager interacts with service brokers using OSB API to provision and manage service instances and service bindings.
The btpoperators.operator.kyma-project.io Custom Resource Definition (CRD) describes the kind and the data format that SAP BTP Operator uses to configure resources.
See the documentation related to the BtpOperator custom resource (CR):
To learn more about the resources the SAP BTP Operator module uses, see Kyma Modules' Sizing.