Exploring the Benefits of the SAP BTP, Kyma runtime

Objectives

After completing this lesson, you will be able to:
  • Describe the benefits of SAP BTP, Kyma runtime compared to a plain Kubernetes cluster
  • Provide at least three arguments of why companies should use SAP BTP, Kyma runtime
  • Explain how SAP provides a managed Kubernetes Cluster with additional features

Vanilla Kubernetes Cluster Versus SAP BTP, Kyma runtime

Installing, updating, and maintaining a Kubernetes cluster is a complex task. If your company is not a cloud provider, you need to hire a team of experts to manage your Kubernetes cluster. This is not only expensive but also time-consuming. You also have to invest a lot of time and money to keep your Kubernetes cluster up to date, which is especially true if you want to use the latest features of Kubernetes and its ecosystem.

To outsource these tasks, a managed Kubernetes service (Kubernetes as a Service) should be considered. With a managed Kubernetes offering, you can fully focus on your business and applications by abstracting away the complexity of managing your Kubernetes cluster and its underlying cloud infrastructure.

SAP Business Technology Platform (SAP BTP) offers a managed Kubernetes service called SAP BTP, Kyma runtime. Unlike a vanilla Kubernetes cluster, SAP BTP, Kyma runtime comes with additional features provided by the Kyma modules. These capabilities were already covered in the previous lesson.

Typically, Kubernetes users would have to decide between different solutions (for example, if they want to use Istio or Linkerd service mesh) for their environment. The decision itself and also the integration, maintenance, and updates of these solutions are time-consuming and complex as well. When you use project "Kyma", the most important tools are already integrated out-of-the-box with the Kyma modules. This saves you a lot of time and money.

However, using Kyma as a managed service will even go one step further and take care of the maintenance and updates of the Kyma modules as well.

How Does SAP Provision and Manage the Managed Kyma runtime?

When you create a Kyma runtime in your SAP BTP subaccount, the underlying Kubernetes cluster is automatically provisioned. In fact, SAP is not hosting the Kubernetes cluster itself but utilizes the compute (VMs), networking and other infrastructure components from Hyperscalers.

SAP provisions the Kubernetes cluster through another SAP-initiated open-source project called Gardener.

Gardener is a Kubernetes cluster manager that delivers fully managed clusters at scale and everywhere you want. All major cloud providers are supported, such as AWS, Azure, GCP, Alibaba, and more. Gardener itself is an officially certified Kubernetes solution.

Technically speaking, Gardener is an extension API server that comes along with a bundle of custom controllers and new custom resources such as garden cluster, seed cluster, shoot cluster, etc.

The garden cluster is the central cluster that manages all the other clusters. The seed cluster is used to provision the actual shoot clusters. Furthermore, the seed cluster reconciles the state of your shoot cluster, performs updates, and ensures that it is always in a healthy and running state.

The shoot cluster is the actual Kubernetes cluster that is provisioned for the Kyma runtime installation.

If you want to learn more about SAP Gardener, you can read the Gardener documentation.

SAP Provision and Management of SAP BTP, Kyma runtime

How Does SAP Provision and Manage the Managed Kyma runtime?

When you create a Kyma runtime in your SAP BTP subaccount, the underlying Kubernetes cluster is automatically provisioned on the Hyperscaler of your choice. SAP provisions the Kubernetes cluster through another SAP-initiated open-source project called Gardener.

Gardener is a Kubernetes cluster manager that delivers fully managed clusters at scale and everywhere you want. All major cloud providers are supported, such as AWS, Azure, GCP, Alibaba, and more. Gardener itself is an officially certified Kubernetes solution.

Technically speaking, Gardener is an extension API server that comes along with a bundle of custom controllers and new custom resources such as garden cluster, seed cluster, shoot cluster, etc.

The garden cluster is the central cluster that manages all the other clusters. The seed cluster is used to provision the actual shoot clusters. Furthermore, the seed cluster reconciles the state of your shoot cluster, performs updates, and ensures that it is always in a healthy and running state.

The shoot cluster is the actual Kubernetes cluster that is provisioned for the Kyma runtime installation.

Garden Cluster with a Gardener managing a Seed Cluster containing a Gardenlet and Control Plane, which in turn manages a Shoot Cluster with multiple nodes.

If you want to learn more about SAP Gardener, you can read the Gardener documentation.

Key Benefits of SAP BTP, Kyma runtime

So, in other words, SAP BTP, Kyma runtime offers the following advantages:

  • A fully managed Kubernetes cluster on a hyperscaler of your choice.
  • The latest features of Kubernetes and its ecosystem.
  • Kyma modules that you can add to your Kyma runtime (SAP BTP Operator, Istio, API Gateway, Serverless, Telemetry, Application Connectivity, and more)
  • Integration with other SAP services and products (for example, SAP BTP services, SAP S/4HANA, SAP SuccessFactors, etc.)
  • Elimination of operations' overhead (zero infrastructure management and maintenance effort).

Summary

In this lesson, you have discovered the benefits of SAP BTP, Kyma runtime compared to a vanilla Kubernetes cluster. Also, you can describe how SAP provisions and operates the managed Kyma runtime.

Further Reading about the Benefits of the SAP BTP, Kyma runtime

Log in to track your progress & complete quizzes