With the SAP BTP service operator, you can consume SAP BTP services from your Kubernetes cluster using Kubernetes-native tools. SAP BTP service operator allows you to provision and manage service instances and service bindings of SAP BTP services so that your Kubernetes-native applications can access and use needed services from the cluster.
The SAP BTP service operator is based on the Kubernetes Operator pattern.

• Architecture
• Prerequisites
• Setup
• Versions
• Using the SAP BTP Service Operator
  • Creating a service instance
  • Binding the service instance
• Reference Documentation
  • Service instance properties
  • Binding properties
  • Passing parameters
  • Managing access
• SAP BTP kubectl Extension
• Credentials Rotation
• Multitenancy

SAP BTP service operator communicates with Service Manager that uses the Open service broker API to communicate with service brokers, acting as an intermediary for the Kubernetes API Server to negotiate the initial provisioning and retrieve the credentials necessary for the application to use a managed service.

It is implemented using a CRDs-based architecture.

• SAP BTP Global Account and Subaccount
• Service Management Control (SMCTL) command line interface. See Using the SMCTL.
• Kubernetes cluster running version 1.17 or higher
• kubectl v1.17 or higher
• helm v3.0 or higher

Back to top

1. Install cert-manager

   • for releases v0.1.18 or higher use cert manager v1.6.0 or higher
   • for releases v0.1.17 or lower use cert manager lower then v1.6.0

2. Obtain the access credentials for the SAP BTP service operator:

   a. Using the SAP BTP cockpit or CLI, create an instance of the SAP Service Manager service (technical name: service-manager) with the plan: service-operator-access
   
   Note
   
   If you can't see the needed plan, you need to entitle your subaccount to use SAP Service Manager service.
   

   For more information about how to entitle a service to a subaccount, see:

   • Configure Entitlements and Quotas for Subaccounts

   
   For more information about creating service instances, see:

   • Creating Service Instances Using the SAP BTP Cockpit

   • Creating Service Instances using SMCTL
     

   b. Create a binding to the created service instance.

   For more information about creating service bindings, see:

   • Creating Service Bindings Using the SAP BTP Cockpit

   • Creating Service Bindings Using SMCTL.

   c. Retrieve the generated access credentials from the created binding:

   The example of the default binding object used if no credentials type is specified:

    {
        "clientid": "xxxxxxx",
        "clientsecret": "xxxxxxx",
        "url": "https://mysubaccount.authentication.eu10.hana.ondemand.com",
        "xsappname": "b15166|service-manager!b1234",
        "sm_url": "https://service-manager.cfapps.eu10.hana.ondemand.com"
    }

   The example of the binding object with the specified X.509 credentials type:

   {
        "clientid": "xxxxxxx",
        "certificate": "-----BEGIN CERTIFICATE-----...-----END CERTIFICATE-----\n-----BEGIN CERTIFICATE-----..-----END CERTIFICATE-----\n-----BEGIN CERTIFICATE-----...-----END CERTIFICATE-----\n",
        "key": "-----BEGIN RSA PRIVATE KEY-----...-----END RSA PRIVATE KEY-----\n",
        "certurl": "https://mysubaccount.authentication.cert.eu10.hana.ondemand.com",
        "xsappname": "b15166|service-manager!b1234",
        "sm_url": "https://service-manager.cfapps.eu10.hana.ondemand.com"
    }

3. Add SAP BTP service operator chart repository

    helm repo add sap-btp-operator https://sap.github.io/sap-btp-service-operator

4. Deploy the the SAP BTP service operator in the cluster using the obtained access credentials:
   

   Note:
   If you are deploying the SAP BTP service operator in the registered cluster based on the Service Catalog (svcat) and Service Manager agent so that you can migrate svcat-based content to service operator-based content, add --set cluster.id=<clusterID> to your deployment script.
   For more information, see the step 2 of the Setup section of Migration to SAP BTP service operator.

   The example of the deployment that uses the default access credentials type:

   helm upgrade --install <release-name> sap-btp-operator/sap-btp-operator \
       --create-namespace \
       --namespace=sap-btp-operator \
       --set manager.secret.clientid=<clientid> \
       --set manager.secret.clientsecret=<clientsecret> \
       --set manager.secret.sm_url=<sm_url> \
       --set manager.secret.tokenurl=<url>

   The example of the deployment that uses the X.509 access credentials type:

   helm upgrade --install <release-name> sap-btp-operator/sap-btp-operator \
       --create-namespace \
       --namespace=sap-btp-operator \   
       --set manager.secret.clientid=<clientid> \
       --set manager.secret.tls.crt="$(cat /path/to/cert)" \
       --set manager.secret.tls.key="$(cat /path/to/key)" \
       --set manager.secret.sm_url=<sm_url> \
       --set manager.secret.tokenurl=<certurl>

Back to top.

Review the supported Kubernetes API versions for the following SAP BTP Service Operator versions.

1. To create an instance of a service offered by SAP BTP, first create a ServiceInstance custom-resource file:

    apiVersion: services.cloud.sap.com/v1
    kind: ServiceInstance
    metadata:
        name: my-service-instance
    spec:
        serviceOfferingName: sample-service
        servicePlanName: sample-plan
        externalName: my-service-instance-external
        parameters:
          key1: val1
          key2: val2

• <offering> - The name of the SAP BTP service that you want to create. To learn more about viewing and managing the available services for your subaccount in the SAP BTP cockpit, see Service Marketplace.

  Tip: Use the Environment filter to get all offerings that are relevant for Kubernetes.

• <plan> - The plan of the selected service offering that you want to create.

2. Apply the custom-resource file in your cluster to create the instance.

   kubectl apply -f path/to/my-service-instance.yaml

3. Check that the status of the service in your cluster is Created.

   kubectl get serviceinstances
   NAME                  OFFERING          PLAN        STATUS    AGE
   my-service-instance   <offering>        <plan>      Created   44s

Back to top

1. To get access credentials to your service instance and make it available in the cluster so that your applications can use it, create a ServiceBinding custom resource, and set the serviceInstanceName field to the name of the ServiceInstance resource you created.

   The credentials are stored in a secret created in your cluster.

  apiVersion: services.cloud.sap.com/v1
  kind: ServiceBinding
  metadata:
      name: my-binding
  spec:
      serviceInstanceName: my-service-instance
      externalName: my-binding-external
      secretName: mySecret
      parameters:
        key1: val1
        key2: val2      

2. Apply the custom resource file in your cluster to create the binding.

   kubectl apply -f path/to/my-binding.yaml

3. Check that your binding status is Created.

   kubectl get servicebindings
   NAME         INSTANCE              STATUS    AGE
   my-binding   my-service-instance   Created   16s
   

4. Check that a secret with the same name as the name of your binding is created. The secret contains the service credentials that apps in your cluster can use to access the service.

   kubectl get secrets
   NAME         TYPE     DATA   AGE
   my-binding   Opaque   5      32s

   See Using Secrets to learn about different options on how to use the credentials from your application running in the Kubernetes cluster,

Back to top

Back to top

To set input parameters, you may use the parameters and parametersFrom fields in the spec field of the ServiceInstance or ServiceBinding resource:

• parameters : can be used to specify a set of properties to be sent to the broker. The data specified will be passed "as-is" to the broker without any modifications - aside from converting it to JSON for transmission to the broker in the case of the spec field being specified as YAML. Any valid YAML or JSON constructs are supported. Only one parameters field may be specified per spec.
• parametersFrom : can be used to specify which secret, and key in that secret, which contains a string that represents the json to include in the set of parameters to be sent to the broker. The parametersFrom field is a list which supports multiple sources referenced per spec.

You may use either, or both, of these fields as needed.

If multiple sources in parameters and parametersFrom blocks are specified, the final payload is a result of merging all of them at the top level. If there are any duplicate properties defined at the top level, the specification is considered to be invalid, the further processing of the ServiceInstance/ServiceBinding resource stops and its status is marked with error condition.

The format of the spec will be (in YAML format):

spec:
  ...
  parameters:
    name: value
  parametersFrom:
    - secretKeyRef:
        name: my-secret
        key: secret-parameter

or, in JSON format

"spec": {
  "parameters": {
    "name": "value"
  },
  "parametersFrom": {
    "secretKeyRef": {
      "name": "my-secret",
      "key": "secret-parameter"
    }
  }
}

and the secret would need to have a key named secret-parameter:

apiVersion: v1
kind: Secret
metadata:
  name: my-secret
type: Opaque
stringData:
  secret-parameter:
    '{
      "password": "letmein"
    }'

The final JSON payload to be sent to the broker would then look like:

{
  "name": "value",
  "password": "letmein"
}

Multiple parameters could be listed in the secret - simply separate key/value pairs with a comma as in this example:

  secret-parameter:
    '{
      "password": "letmein",
      "key2": "value2",
      "key3": "value3"
    }'

Back to top.

By default, the SAP BTP operator has cluster-wide permissions.
You can also limit them to one or more namespaces; for this, you need to set the following two helm parameters:

--set manager.allow_cluster_access=false
--set manager.allowed_namespaces={namespace1, namespace2..}

Note:
If allow_cluster_access is set to true, then allowed_namespaces parameter is ignored.

The SAP BTP kubectl plugin extends kubectl with commands for getting the available services in your SAP BTP account by using the access credentials stored in the cluster.

• jq

• The SAP BTP kubectl plugin is currently based on bash. If you're using Windows, you should utilize the SAP BTP plugin commands from a linux shell (e.g. Cygwin).

• Download https://github.com/SAP/sap-btp-service-operator/releases/download/<release>/kubectl-sapbtp
• Move the executable file to any location in your PATH

The list of available releases: sapbtp-operator releases

  kubectl sapbtp marketplace -n <namespace>
  kubectl sapbtp plans -n <namespace>
  kubectl sapbtp services -n <namespace>

Use the namespace parameter to specify the location of the secret containing the SAP BTP access credentials.
Usually it is the namespace in which you installed the operator. If not specified, the default namespace is used.

Back to top.

To enable automatic credentials rotation, you need to set the following parameters of the credentialsRotationPolicy field in the spec field of the ServiceBinding resource:

• enabled - Whether the credentials rotation option is enabled. Default value is false.
• rotationFrequency - Indicates the frequency at which the credentials rotation is performed.
• rotatedBindingTTL - Indicates for how long to keep the rotated ServiceBinding.

Valid time units for rotationFrequency and rotatedBindingTTL are: "ns", "us" or ("µs"), "ms", "s", "m", "h".

status.lastCredentialsRotationTime indicates the last time the ServiceBinding secret was rotated.
Please note that credentialsRotationPolicy evaluated and executed during control loop which runs on every update or during full reconciliation process.

During the transition period, there are two (or more) ServiceBinding: the original and the rotated one (holds the services.cloud.sap.com/stale label), which is deleted once the rotatedBindingTTL duration elapses.

You can also choose the services.cloud.sap.com/forceRotate annotation (value doesn't matter), upon which immediate credentials rotation is performed. Note that the prerequisite for the force action is that credentials rotation enabled field is set to true.).

Note:
It isn't possible to enable automatic credentials rotation to an already-rotated ServiceBinding (with the services.cloud.sap.com/stale label).

Back to top

You can configure the SAP BTP service operator to work with more than one subaccount in the same Kubernetes cluster. This means that different namespaces can be connected to different subaccounts. The association between a namespace and a subaccount is based on a different set of credentials configured for different namespaces.

To connect the namespace to a subaccount, you first have to obtain the access credentials for the SAP BTP service operator and then maintain them in a secret that is specific for that namespace.

There are two options to maintain namespace-specific credentials, and they differ between default and TLS-based access credentials types:

• Define a secret named sap-btp-service-operator in the namespace. ServiceInstance and ServiceBinding that are applied in the namespace will belong to the subaccount from which the credentials were issued.
• Define different secrets for different namespaces in a centrally managed namespace, following the secret naming convention: sap-btp-service-operator-<namespace>.

apiVersion: v1
kind: Secret
metadata:
  name: sap-btp-service-operator
  namespace: <namespace>
type: Opaque
data:
  clientid: "<clientid>"
  clientsecret: "<clientsecret>"
  sm_url: "<sm_url>"
  tokenurl: "<auth_url>"
  tokenurlsuffix: "/oauth/token"

• Define a secret pair named sap-btp-service-operator and sap-btp-service-operator-tls in the namespace. ServiceInstance and ServiceBinding that are applied in the namespace will belong to the subaccount from which the credentials were issued.
• Define different secrets for different namespaces in a centrally managed namespace, following the secret naming convention: sap-btp-service-operator-<namespace> and sap-btp-service-operator-tls-<namespace> . For more information, see tls secret.

apiVersion: v1
kind: Secret
metadata:
  name: sap-btp-service-operator
  namespace: <namespace>
type: Opaque
data:
  clientid: "<clientid>"
  sm_url: "<sm_url>"
  tokenurl: "<auth_url>"
  tokenurlsuffix: "/oauth/token"

apiVersion: v1
kind: Secret
metadata:
  name: sap-btp-service-operator-tls
  namespace: <namespace>
type: kubernetes.io/tls
data:
  tls.crt: <crt> #base64 encoded
  tls.key: <key> #base64 encoded

Notes:

• If none of the those mentioned above options are set, sap-btp-service-operator secret of a release namespace is used.
  See step 4 of the Setup section.

Back to top

You're welcome to raise issues related to feature requests, bugs, or give us general feedback on this project's GitHub Issues page. The SAP BTP service operator project maintainers will respond to the best of their abilities.

We currently do not accept community contributions.

This project is licensed under Apache 2.0 unless noted otherwise in the license file.

Back to top