Kyma Runtime
Kyma Runtime is SAP BTP's managed Kubernetes environment for building and running cloud-native extensions, microservices, and event-driven integrations that connect to SAP and non-SAP systems. This topic covers its business purpose, provisioning and lifecycle within a BTP subaccount, core Kubernetes concepts as applied in Kyma, connectivity and security patterns, deployment workflows, observability, and how it differs operationally from Cloud Foundry and ABAP-based extension approaches.
Overview
Kyma Runtime is SAP BTP's managed Kubernetes environment for building and running cloud-native extensions, microservices, and event-driven integrations that connect to SAP and non-SAP systems. This topic covers its business purpose, provisioning and lifecycle within a BTP subaccount, core Kubernetes concepts as applied in Kyma, connectivity and security patterns, deployment workflows, observability, and how it differs operationally from Cloud Foundry and ABAP-based extension approaches.
Lessons in this topic
- BTP Kyma Part 1: What Kyma Runtime Is and When to Use ItKyma is SAP's managed Kubernetes runtime on BTP. Learn what it offers (namespaces, deployments, services, modules like Istio, API Gateway, Serverless and Eventing), how it integrates with BTP services, and when to choose it over Cloud Foundry.
- BTP Kyma Part 2: Deploying and Exposing a ServiceDeploy a containerized service to Kyma end to end: build and push an image, create deployment and service manifests with resources and probes, bind BTP services via the operator, and expose the service externally with an APIRule — then verify and troubleshoot.
- BTP Kyma Part 3: APIRules, Istio and Securing WorkloadsSecure Kyma workloads: APIRules with JWT validation against your identity provider, Istio sidecars and mutual TLS inside the cluster, authorization policies, network policies, secrets handling and namespace isolation — plus troubleshooting 401/403/503 errors.
Interview questions covered
- What are the core concepts of Kyma Runtime, and how would you explain them clearly in an SAP interview?
- How would you apply Kyma Runtime in a real SAP project? Walk through the design or implementation approach.
- A production issue is reported in Kyma Runtime. What would you check first, and how would you troubleshoot it systematically?
- What are the most important design decisions, trade-offs, and best practices in Kyma Runtime?
- Suppose you inherit an existing Kyma Runtime solution. How would you review it before making a change?
- Walk through deploying and exposing a containerized service on Kyma.
- A retail customer needs an event-driven microservice reacting to S/4HANA events. When would you choose Kyma and why?
- Calls to a Kyma API return 401/403/503 intermittently. How do you secure and troubleshoot it?