BTP Kyma Part 1: What Kyma Runtime Is and When to Use It
Kyma 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.
What this complete series covers
Learn Kyma Runtime in a clear, practical sequence — from the basic idea to real project use, troubleshooting, and interview-ready understanding.
- Who it is for
- Best for SAP consultants, developers, and learners who want a practical understanding of Kyma Runtime.
- Prerequisites
- A basic understanding of SAP BTP helps. Hands-on steps may require a BTP subaccount and access to the relevant Integration Suite or BTP service.
- Final outcome
- By the end, you should be able to explain Kyma Runtime clearly, follow the main end-to-end flow, apply it in a project scenario, and troubleshoot the most common issues.
- Part 1: BTP Kyma Part 1: What Kyma Runtime Is and When to Use It
Introduces Kyma Runtime as SAP BTP's managed Kubernetes offering, explaining its purpose, when to choose it over Cloud Foundry, and how it fits into the subaccount/entitlement model.
- Part 2: BTP Kyma Part 2: Deploying and Exposing a Service
Walks through deploying a workload to Kyma, exposing it via APIRule with authentication, and connecting it to BTP services like Destination service for secure outbound calls.
- Part 3: BTP Kyma Part 3: APIRules, Istio and Securing Workloads
Learn how to expose microservices running in Kyma Runtime to external callers using API Rules, and how to secure those endpoints with Istio-based authentication, mTLS, and OAuth2 p
System and release assumptions: SAP BTP services evolve regularly. Capability names, screens, and setup steps can differ by region, entitlement, and tenant version; the core design principles remain the same.
Explanation
📌 KEY POINTS
✅ Kyma is a managed Kubernetes cluster provisioned from a BTP subaccount.
✅ Workloads are containers in deployments and services within namespaces.
✅ Modules add capabilities: Istio (service mesh), API Gateway (APIRules), Serverless (functions), Eventing.
✅ BTP services are consumed via the BTP service operator (ServiceInstance/ServiceBinding resources).
⚠️ Kyma needs Kubernetes skills — without them, Cloud Foundry is often the better choice.
━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS
Part 1: What Kyma is
Part 2: Deploying and exposing a service
Part 3: APIRules, Istio and security
━━━━━━━━━━━━━━━━━━━━
▶ 1. KUBERNETES BASICS
- Namespace, deployment, pod, service.
━━━━━━━━━━━━━━━━━━━━
▶ 2. KYMA MODULES
- Istio, API Gateway, Serverless, Eventing.
━━━━━━━━━━━━━━━━━━━━
▶ 3. BTP INTEGRATION
- Service operator; secrets from bindings.
━━━━━━━━━━━━━━━━━━━━
▶ 4. TOOLS
- kubectl, kubeconfig, Kyma dashboard.
━━━━━━━━━━━━━━━━━━━━
▶ 5. WHEN TO USE
- Containers, microservices, event-driven, custom tooling.
━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP
- Enable Kyma in a subaccount.
- Download kubeconfig and list namespaces.
- Deploy a sample container.
✅ CHECKPOINT: pod running in your own namespace.
Code example
===== BASICS =====kubectl create namespace orderskubectl apply -n orders -f deployment.yamlkubectl get pods -n orders ===== BTP SERVICE VIA OPERATOR =====apiVersion: services.cloud.sap.com/v1kind: ServiceInstancemetadata: { name: orders-xsuaa }spec: { serviceOfferingName: xsuaa, servicePlanName: application }---kind: ServiceBinding → secret with credentials mounted into the podReal project scenario
A retail customer needed a custom event-driven microservice reacting to S/4HANA events. Kyma with Eventing and Serverless fit the pattern, and the team had Kubernetes skills — delivery was fast.
Common mistakes
- Kyma without K8s skills.
- Default namespace.
- Hard-coded secrets.
- Ignoring modules.
- No resource limits.
Best practices
- Choose by skills.
- Namespaces per app/team.
- Service operator bindings.
- Enable needed modules.
- Set limits.
Interview angle
Questions: "What is Kyma?", "Kyma vs Cloud Foundry?", "How do Kyma apps use BTP services?"
Strong answer: managed K8s, workloads, modules, service operator, choice criteria.
Practice this lesson
Quick check
1. Interviewers often ask candidates to explain the difference between Cloud Foundry and Kyma environments on BTP and when to choose each. In the Kyma Runtime context, which answer shows the strongest practical judgment?
2. A team without Kubernetes skills plans to use Kyma for a simple CAP app. What is the better advice?
3. What is Kyma runtime on SAP BTP?
Interview questions
1. What are the core concepts of Kyma Runtime, and how would you explain them clearly in an SAP interview?
Answer it in your own words first, then compare.
2. A retail customer needs an event-driven microservice reacting to S/4HANA events. When would you choose Kyma and why?
Answer it in your own words first, then compare.
Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.