You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Kyma provisioning automation with a cis-local service
download kubeconfig (from the cis payload) or/and create a service account
link ArgoCD to this new kyma cluster (via automation)
deploy a BTP multi-tenant application to kyma cluster with ArgoCD automation
Reasons / Value proposition / Success criteria
BTP Kyma Runtime development.
Solution architecture and adoption.
Seamless deployment of SaaS provider applications to kyma environments.
This scenario is showcasing the usage of SAP BTP services with the kyma runtime environment with the focus on the synergy/share-ability/portability with all the other BTP services with the aim of simplifying the housekeeping of multi-tenant SaaS applications.
By design, this eliminates the need of any human interaction with a kyma cluster;
The SaaS application provider runs the automation scripts and SaaS solution becomes ready for consumers from the get-go.
The automation routine itself might be delivered as a BTP trial booster application, or, eventually, could be implemented as an internal BTP service (similar to SAP BTP ArgoCDaaS)
Alternatively, the automation scripts can be made public on SAP Samples with instructions how to assemble them into a routine.
Description
Seamless deployment of SaaS provider applications to kyma environments
The rehearsed automation use case, part of kyma cli effort, is as follows:
a BTP trial account with a default trial subaccount (= service provider)
ArgoCD service deployed either on SAP's or on customer's devops landscape
Reasons / Value proposition / Success criteria
This scenario is showcasing the usage of SAP BTP services with the kyma runtime environment with the focus on the synergy/share-ability/portability with all the other BTP services with the aim of simplifying the housekeeping of multi-tenant SaaS applications.
By design, this eliminates the need of any human interaction with a kyma cluster;
The SaaS application provider runs the automation scripts and SaaS solution becomes ready for consumers from the get-go.
The automation routine itself might be delivered as a BTP trial booster application, or, eventually, could be implemented as an internal BTP service (similar to SAP BTP ArgoCDaaS)
Alternatively, the automation scripts can be made public on SAP Samples with instructions how to assemble them into a routine.
Attachments
Getting an Access Token for SAP Cloud Management Service APIs | SAP Help
https://help.sap.com/docs/btp/sap-business-technology-platform/getting-access-token-for-sap-cloud-management-service-apis#procedure
Managing Service Resources Using the APIs of the SAP Service Manager | SAP Help
Consuming Services in Other Environments Using the SAP Service Manager Instances | SAP Help
Get Access to the APIs Using the apiaccess Service Plan | SAP Help
Configure Custom SAP IAS tenant with SAP BTP Kyma runtime environment | SAP Blogs
getting-on-the-kubernetes-ladder-with-sap-btp | gists
SAP Kyma deployments easy with ArgoCD multiple-sources apps | SAP Blogs
ArgoCD as a Service
#18198
The text was updated successfully, but these errors were encountered: