Kyma APIRule for Exposing Services to the Internet
Tutorials that teach this
- Tutorial Fast Prototyping in SAP BTP, Kyma Runtime Using App Push
- Tutorial Create and Configure the Approuter Application for a Multitenant Application
- Tutorial Create Kyma Function and a Microservice via UI
- Tutorial Implement Subscription Callbacks for a Multitenant Application
- Tutorial Deploy a Go MSSQL API Endpoint in SAP BTP, Kyma Runtime
- Tutorial Consume SAP BTP Services In SAP Kyma
Prerequisites
- Concept Kyma Istio Service Mesh Module
- Concept Creating a Kyma Serverless Function
- Concept Istio Sidecar Injection in Kyma Namespaces
- Concept Kyma APIRule noAuth Access Strategy The `noAuth` access strategy is a configuration option for a Kyma **APIRule** resource that exposes an API endpoint without requiring any authentication. Developers use it when they want to make a service publicly accessible, such as when deploying a mock application that needs to receive unauthenticated inbound requests in SAP BTP, Kyma Runtime.
- Concept Istio Service Mesh Istio Service Mesh is an infrastructure layer that developers use to manage, secure, and observe communication between services in a Kubernetes-based environment. On SAP BTP, developers use the [Istio module](https://help.sap.com/docs/btp/sap-business-technology-platform/26ffe00c24574db58697992b93f397ac?locale=en-US&state=PRODUCTION&version=Cloud) to manage and configure the Istio service mesh. A key feature of Istio is its sidecar proxy, which is injected into Pods to handle traffic management and enforce policies; developers can consult the [Istio Service Mesh documentation](https://help.sap.com/docs/btp/sap-business-technology-platform/ca84edb503ce4999b07237e5eed9eefc?locale=en-US&state=PRODUCTION&version=Cloud) to understand what sidecar proxies are, the benefits they provide, and how to troubleshoot injection issues when Pods do not have a sidecar proxy injected.
- Concept Deploying Applications to SAP BTP, Kyma Runtime
- Concept Deploying a Microservice to Kyma Runtime