SAP Kyma using BTP Connectivity Service

[timrehrmann]

Hello!

We have some problems connecting to our on premise S/4 HANA system from Kyma using SAPs connectivity service.

We followed this sample:

https://github.com/SAP-samples/kyma-runtime-extension-samples/tree/main/connectivity-proxy

However, when we create the Connectivity Service via Kyma Dashboard, there is no connectivity proxy pod created.

When we created the services via the service yaml file, we get two running connectivity proxy pods as seen in the screenshot:

When we test the service with the curl command, it doesn't know the proxy address:

Also, when we run our application we get the following error message:

com.sap.cloud.sdk.cloudplatform.connectivity.exception.DestinationAccessException: Failed to configure on-premise proxy for destination 'DEST_NAME'. Please make sure to correctly bind your application to a service instance.

Our yaml file is structed as following:

apiVersion: servicecatalog.k8s.io/v1beta1
kind: ServiceInstance
metadata:
  name: connectivity-smartfi-controller
spec:
  clusterServiceClassExternalName: connectivity
  clusterServicePlanExternalName: connectivity_proxy

---
apiVersion: servicecatalog.k8s.io/v1beta1
kind: ServiceBinding
metadata:
  name: connectivity-smartfi-controller-binding
spec:
  instanceRef:
    name: connectivity-smartfi-controller

Thanks in advance and kind regards,

Tim

[quovadis]

Tim, regarding the connectivity proxy creation we have provides several replies;

Re the use of BTP destinations: not sure what might have gone wrong at your end.

here follows a complete blog/tutorial on connectivity proxy used with a BTP destination to talk to an S/4HANA on premise....

https://blogs.sap.com/2022/04/07/veridisquo.-reaching-sap-lob-destinations-with-connectivity-proxy-a...

kind regards; Piotr

[jamie_cawley]

Can you check that the services have been created by running?

kubectl get svc -n kyma-system | grep connect

[timrehrmann]

kubectl get svc -n kyma-system | grep connect
central-application-connectivity-validator                ClusterIP   100.71.151.169   <none>        8081/TCP,8080/TCP
 62d
connectivity-proxy                                        ClusterIP   100.65.187.115   <none>        20003/TCP,20004/TCP
 160m
connectivity-proxy-tunnel                                 ClusterIP   None             <none>        8042/TCP
 160m
connectivity-proxy-tunnel-0                               ClusterIP   100.67.226.172   <none>        8042/TCP
 160m
connectivity-proxy-tunnel-healthcheck                     ClusterIP   100.70.126.84    <none>        8042/TCP
 160m

Seems like the services have been created