The document describes the steps needed to connect an external system (for example, HTTPBin) with Kyma runtime.
In this example, Kyma sends authenticated requests to an external service.
- Create Kyma runtime either by using the SAP BTP cockpit or by following the Kyma Quick Install tutorial.
- Besides the Kyma default modules like Istio and API Gateway, you must enable the following Kyma modules:
- Application Connector: it includes the Application Gateway for proxying requests to external systems.
- Serverless: used to run a Function that sends an HTTP request to an external system. If you created Kyma runtime using SAP BTP cockpit, follow this tutorial for Adding and Deleting a Kyma Module. Alternatively, continue with the steps described in the Kyma Quick Install tutorial.
- Create an Application custom resource (CR). The Application CR represents an external system and contains all information about exposed endpoints and their security configuration etc.
- Register a service for the external system in the Application CR. The service is an abstraction of the external system. Kyma workloads can send their requests to the service URL, and the Application Gateway proxies these requests to the external system and handles all security-related aspects transparently (for example, establishing a trusted connection or authentication).
- Register a secured API. The Application Connector module supports many different authentication methods. In this step, you can find an example for each of them.
- Disable TLS certificate validation. For testing purposes, disabling the TLS certificate validation can be helpful. By default, the Application Connector module validates TLS certificates when establishing a secure connection.
- Call the external API. In this step, you can learn how to call an external system using a Kyma Function.