-
Notifications
You must be signed in to change notification settings - Fork 405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seamless deployment of SaaS provider applications to kyma environments #18666
Comments
The proposed architecture of the multi-tenant SaaS provider application. The multi-tenant application will offer out-of-the box routines for integration with popular SAP and non-SAP LOBs, namely:
The frontend is a build apps react-native application (SAP Build, SAP Build Apps) deployed natively to kyma environment
non-SAP solutions:
Attachments: Mistral gagnant. Mistral AI and SAP Kyma serverles... - ( a week ago ) Deploy SAP Build Apps web applications easy to SAP BTP, Kyma runtime. |
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. |
All the automation obstacles have been lifted including the procurement of a headless kubeconfig with a short-lived id_token: https://gist.github.com/ptesny/14f49f49e0fbe2a3143700ce707ee76b#file-bdc-landscape-automation-md |
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. |
unstale |
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: