Deploy in SAP BTP, Kyma Runtime

SAP BTP, Kyma runtime is a cloud-native application runtime that combines the power of Kubernetes with a set of best-in-class tools and open-source components that empower you to develop, run, and operate secure and scalable cloud-native applications. Detailed information is available at Kyma Environment.

The Kyma runtime for SAP BTP’s files are provided as a container image. In addition, since the containers run on Kubernetes, their configuration is described by Kubernetes resources.

Hence, you need two kinds of artifacts to run applications on Kubernetes:

• Container images
• Kubernetes resources

You start by building your project as container images and push those images to a container registry of your choice. Then, you add a CAP Helm chart to your project. As a last step, you deploy the Helm chart to your Kyma resources, where service instances of SAP BTP services are created and pods pull the previously created container images from the container registry.

1. Choose KubeconfigURL under the Kyma Environment tab in your subaccount.

   

   A file kubeconfig.yaml is downloaded.

   

2. Copy the kubeconfig.yaml file to the ~/.kube/ directory and rename it to config. Replace or rename any existing file with the same name.

There are two additional steps for Windows users only:

1. Go to C:\ProgramData\chocolatey\bin.

2. Rename kubelogin.exe to kubectl-oidc_login.exe.

1. Skip this step if you cloned the application from the Incident Management application GitHub repository without going through the application development steps. Perform this step only in case you have developed the application from scratch following the tutorials in the Develop a Full-Stack CAP Application Following SAP BTP Developer’s Guide group.

   1. In SAP Business Application Studio, choose the icon to download dev space content.

      

      Make sure the IncidentManagement dev space is in status RUNNING.

   2. Extract the incident-management folder from the downloaded archive.

2. Open a command line window in the folder where your application resides (for example, incident-management if developed from scratch or incidents-app if cloned from GitHub) and run the following command to open the project in VS Code:

   bash

   Copy

   code .
   

CAP provides a configurable Helm chart for Node.js applications.

1. Run the following command in your project root folder:

   bash

   Copy

   cds add helm --y
   

   As a result, you’ll see a newly-created chart folder in your project. The chart folder holds the helm configuration, including the values.yaml file where you’ll add your container image settings later on.

2. Add your container image settings to your chart/values.yaml file:

   yaml

   Copy

   global:
     domain: 
     imagePullSecret:
       name: 
     image:
       registry: <your-container-registry>
       tag: <image-version>
   

   Make sure to replace <your-container-registry> with the link to your container registry and keep in mind that <image version> should be a string.

   If you’d like to overwrite the global image version, you can add a tag for each image. Here’s an example:

   yaml

   Copy

   srv:
     image:
       repository: incident-management-srv
       tag: <incident-management-srv-image-version>
   

3. Run the following command to get the domain name of your Kyma cluster:

   bash

   Copy

   kubectl get gateway -n kyma-system kyma-gateway \
           -o jsonpath='{.spec.servers[0].hosts[0]}'
   

   Result should look like this:

   bash

   Copy

   *.<xyz123>.kyma.ondemand.com
   

   <xyz123> is a placeholder for a string of characters that’s unique for your cluster.

4. Add the result without the leading *. in the domain property to the chart/values.yaml file so that the URL of your CAP service can be generated:

   yaml

   Copy

   global:
       domain: <your-cluster-domain>
   ...