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 the requirements for the Kyma runtime: subaccounts and entitlements
using the BTP cockpit web UI, user interface, and the BTP CLI, command line interface.
I am connected here to the SAP BTP Cockpit, with a global account called
global and a subaccount called subaccount, trying to keep thing simple here,
as most of you will know, the global account is the commercial vehicle, containing the services
you are entitled to use either through the cloud platform enteprise agreement, CPEA, or
pay-as-you-go, and then we also a free trial and a free tier, but we will be focussing on
the enterprise environment for this video. First, let’s check the service assignments
Is the Kyma runtime service assigned to our global account?
If you have a lot of entitlements, you can enter kyma in the search box, and yes, we are
entitled to start the kyma runtime in azure, aws, and, or, gcp, the Google Cloud Platform.
Now, you might see only one or two, or none at all, and in this case you would need
to contact SAP, this is not self-service. The service assignments needs to be added,
enabled for your global account. OK - that’s the first step. Check.
Next, we switch to the entity assigment, and the entity here is your subaccount.
Now, I have only one subaccount but I would like to have one subaccount for each of the cloud
providers, so let’s set this up first. Account Explorer,
Create, Subaccount
First, pick your region Here they are all listed
I will start with Europe Frankfurt under AWS, but you can take any
region or cloud provider of preference Enter a display name, which is what is says,
for display here in the cockpit, can be changed at any time
the subdomain needs to be unique for the provider, hence some random characters are appended,
and optionally a description Under advanced, you can select whether this
is for production, to enable beta features, or add labels, to used for billing purposes, for example.
Create Takes a few seconds
Basically, creates an account with the cloud provider, all metadata, no resources, no charges .
To create the other two subaccount, I’ll use the CLI
btp create accounts/subaccount with display name, region, and subdomain.
Just to show that you can easily script the creation of a Kyma environment, if you prefer.
Back to the cockpit, refresh
and here we have our subaccounts. Very well
So now we can return to the entity assignments,
and select an entitiy, a subaccount that is Go
Search Kyma nothing there, as expected
Configure entitlements Add Service plans
Entitlement Search Kyma
The entitlement is available select aws (Environment)
Add 1 Service Plan Save
Takes a few seconds, again just metadata,
and the entitlement is listed Now we only have a single unit,
so we can only create a single cluster. Should you need more you need to make sure more
units are assigned to your global account. Back the CLI
list accounts/subaccount shows us the subaccount id
with the list accounts/entitlement and subaccount parameter
we can query the entitlements for the subaccount
and for our AWS subaccount we can see service name kymaruntime, plan aws, with quota 1 listed
with assign accounts/entitlements we can add the entitlement also to our azure and gcp account
and if we then return to the cockpit and select our three subaccounts,
filter on kyma, we can see that
the entitlements are properly assigned Very well. So much for the prerequisites.
In the next video, we cover creating the Kyma runtime.
This video tutorial was recorded by Denys van Kempen, SAP HANA Academy / SAP
Partner Innovation Lab Any good? Give us a like.
For updates, don’t forget to subscribe. Thanks for watching.