Connect SAP Private Link Service to Google Cloud Private Service Connect (Kyma)

Requires Customer/Partner License | Beginner | 10 min. Tags: SAP Private Link service, Beginner, SAP BTP cockpit, Tutorial, SAP Business Technology Platform, SAP BTP command line interface

Connect SAP Private Link service to Google Cloud Private Service Connect and bind the service instance on a Kyma cluster.

Step 1: Check offerings of Private Link service

After you’ve logged in as described in Enable SAP BTP, Kyma Runtime Using the Command Line, you can check all available entitlements for your subaccount. Open a command prompt and enter the following command:

btp list accounts/entitlements

You can now see a list of service names and service plans, as shown in this example:

$ btp list accounts/entitlements
Showing entitlements for subaccount 9be57735-1234-1234-1234-0123456789ab:
service name service plan quota
...
privatelink standard 8
...

Make sure you can find privatelink under the service name column in the output.

Step 2: Get Resource-ID for Google Cloud Private Service Connect

To create and enable a private link, you need to define the connection to the service first. To do so, you need the Service attachment:

1. Go to the Google Cloud console.
2. Navigate to the Private Service Connect for which you want to find out the Service Attachment, for example: Private Service Connect > Published services.
3. Select a published service and copy its Service Attachment path.

Step 3: Make sure SAP BTP Operator module is enabled

SAP BTP Operator module btp-operator must be enabled before creating and managing SAP Private Link Service Instances in Kyma. Otherwise, you get the following error message: resource mapping not found for {...} ensure CRDs are installed first. Additionally, it is required that btp-operator module is version 1.1.0 or newer. To enable the btp-operator module, follow the procedure described in Enable and Disable a Kyma Module.

Step 4: Create private link service

Currently, you do not have any service instances enabled. Therefore, you need to create one. To create a new private link, you need the following information:

• offering (privatelink),
• plans (standard),
• a unique name (for instance, privatelink-test),
• and the Service Attachment path from Google Cloud console (for example, projects/<gcp-project>/regions/<gcp-region>/serviceAttachments/<my-service-attachment>).

Enter the following command and fill in the necessary information:

kubectl create -f - <<EOF
apiVersion: services.cloud.sap.com/v1
kind: ServiceInstance
metadata:
  name: privatelink-test
spec:
  serviceOfferingName: privatelink
  servicePlanName: standard
  parameters:
    resourceId: "projects/<gcp-project>/regions/<gcp-region>/serviceAttachments/<my-service-attachment>"
    requestMessage: Please Approve
EOF

Step 5: Ensure private link was created successfully

To check the current status of the newly created service instance, you need the name of your service instance (in this example privatelink-test). Type in the following:

kubectl get ServiceInstance privatelink-test -o wide

You should see the following success message:

NAME                   OFFERING      PLAN       STATUS     READY   AGE   ID            MESSAGE
privatelink-test       privatelink   standard   Created    True    2m    <some UUID>   ServiceInstance provisioned successfully

Step 6: Create a service binding for the service instance

When service binding is created Private Link service enables network access to the IP address associated with the Private Endpoint. To create a new binding, you need the following information:

• unique name of the binding (for example privatelink-binding-test)
• the name of the service instance (privatelink-test)
• unique name of the secret that will be created (for example privatelink-secret-test)

Enter the following command to create a new binding with the example information:

kubectl create -f - <<EOF
apiVersion: services.cloud.sap.com/v1
kind: ServiceBinding
metadata:
  name: privatelink-binding-test
spec:
  serviceInstanceName: privatelink-test
  secretName: privatelink-secret-test
EOF

If the command is successful, a kubernetes secret with the same name as specified in secretName is created. The secret stores information about the private link endpoint in its hostname field. Use the following command to print the hostname field from the secret:

kubectl get secret privatelink-secret-test -o jsonpath='{.data.hostname}' | base64 --decode

As an example, the output might look like the following:

000000-000000-0000-0000-07a4762eceb6.pls.sap.internal

Follow the steps in Configure DNS on Kyma.

Congratulations! You have successfully completed the tutorial.