Picked up · Cloud DEEN

One Kyma cluster, several subaccounts: mapping namespaces cleanly

community.sap.comChristianWeiss, SAP · 29 January 2026 Mastering Kyma Multi-Tenancy: Mapping namespaces to different BTP Subaccounts Go to source ↗
Picked up by Siegfried Zeilinger · AI-assisted: editing, translation
Diesen Beitrag auf Deutsch lesen

Why it's worth reading

A Kyma cluster for every application is a fine idea with a hefty price tag. By default, every service instance lands in the subaccount where the cluster was created. The post shows how to point the SAP BTP Service Operator at a separate provider subaccount for each namespace, by hand or with Terraform. One cluster, several applications, entitlements kept apart.

Better architecture and a smaller bill in one go. That doesn’t happen every day.

More finds

community.sap.comSAP Cloud ALM: the ITSM Console shows every call to the ticketing systemnews.sap.comJoule Studio and NVIDIA OpenShell: how SAP plans to keep AI agents on a leashgithub.comTerraform and entitlements: where depends_on belongs

Discussion

Submitting stores your name, email and comment. See our privacy policy.