Hi, my name is Denys van Kempen, SAP HANA Academy and SAP’s Partner Innovation Lab
In this video tutorial series we are going to explore the Kyma runtime of the SAP Business
Technology platform.
This video was recorded in January 2022.
For the latest tutorials on the topic, please check the playlist.
In this video, we cover enabling he Kyma runtime: creating a service instance using the BTP
cockpit and the BTP CLI.
Welcome back.
In the previous video we covered the requirements, subaccount and entitlement.
Now we are ready to create the Kyma runtime.
We are in the BTP cockpit account explorer.
Overview page for our AWS subaccount cf-eu10, we created in the previous video.
If you have enabled Cloud Foundry before from the subaccount view, you might be tempted
to enable Kyma similarly by clicking the button.
However, if you have checked the documentation, you might have noticed this is considered
the legacy method and we are recommended to go to the service market place.
What’s the difference?
Well, it is here, under step 2 additional parameters, as we will see, using the other
dialog will give us access to the parameters in JSON format and this allows for more customisation
and automation.
Services Service Marketplace
Kyma environment Create
Three steps: 1.
Basic info Here we need to provide service, plan, and
instance name.
Note the information message: Enabling the Kyma environment may take between 30 minutes
and an hour.
It is a little less, actually, but with Kyma we are creating a Kubernetes cluster, so first
the virtual machines, then Kubernetes, then deploy Kyma, all components, and this takes
some time.
As instance name, as indicated, a CLI-friendly name is recommended, no spaces or special
characters (including accents).
The instance name is optional.
If we don’t provide one, the subaccount domain name with the subaccount name appended
is being used.
2.
Parameters: Note that we now have a Form and a JSON tab
Here we get to name the cluster.
This time, a required parameter, defaults to the subaccount domain name.
Then we get to select the region for the cluster.
As a reminder, the cluster regions are documented, we have covered this in a previous video.
eu-central-1 corresponds to the region of my subaccount but these do not need to match.
Machine type m5, 2x, 4x, 8x or 12x large, these are AWS virtual machine configurations.
You can look the specs up in the AWS documentation The Kubernetes cluster will be running an
VMs and here you can specify how much memory and CPU should be allocated to each VM.
2x corresponds to 8 vCPUs and 32 GB of RAM, 12x is times 6
Then we also need to set the autoscaler, with 2 machines at a minimum and 10 max, default
settings, but this is configurable, and also modifyable once the cluster is created.
Here we have the parameters in JSON format.
We can copy the JSON parameters and save to a file and use this as input for the CLI to
create a service instance or for next time when using the cockpit.
Step 3.
Review Click create to create.
How does this look like for the other cloud providers?
Let’s switch to Azure, in the 20 range Still in the service marketplace.
Kyma environment Create
Using the shortcut menu from the tile, no need to select it first.
Same dialog The difference is with Step 2
Of course we now get to see the Azure regions and Azure machine types, a single entry, standard_d8_v3;
that’s 8 vCPUs and 32 GB of RAM, one size fits all.
But we can specify the number of virtual machines, we need
with the JSON formatting There might be other parameters, but this
is not currently not documented.
OK, let’s cancel this and switch to Google Cloud, in the 30 range
Kyma environment Create
Parameters Here we have three regions we can choose from
to host the Kubernetes cluster and four machine types
These are the same as for AWS: 8, 16, 32, or 48 CPUs
in JSON format, you can just copy paste this to a file
OK, let’s create the Kubernetes cluster, we are back now to the AWS subaccount
Little information dialog, creation in progress
You can view the status on the Instances and subscriptions page, under environments.
This will be spinning for a while Fast forward
Cluster created On the menu
Update, view parameters, add labels, and delete View parameters shows the JSON again, this
time with a copy JSON button, again so we can save this to a file for use with the BTP
CLI command line.
With update we can make changes to the maximum and minimum number of virtual machines.
Note that there is no option to stop and start the cluster.
Once a cluster is created it is up and running, 24/7.
OK, and then we can go to the Dashboard but, alas
we do not have enough permissions, and we need to contact our administrator to grant
access.
Well, that’s us, and we will take a look in the next video how we can fix this.
Before we go, a brief look at the BTP CLI We can use the create accounts/environment-instance
command specifying the subaccount ID, the environment (kyma), the service (kymaruntime),
plan (aws, azure, or gcp) and for parameters pass the JSON in either on the command line
escaping the double quotes with a backslash, or more conveniently, with an input file,
here we are using a file named azure.json
The prompt is returned immediately but, as mentioned, creating the runtime will take
a while.
That’t it.
In the next video, we cover role collections and authorisations, so we can access the dashboard.
This video tutorial was recorded by Denys van Kempen, SAP HANA Academy / SAP Partner
Innovation Lab For updates, don’t forget to subscribe.
Thanks for watching.