Official Support for multiple tenant units for Self Hosted Custom Edition

Even the concept of Tenant Units is documented publicly on the installing self hosted custom edition documentation (https://www.ibm.com/docs/en/instana-observability/current?topic=ice-installing#required-resources-custom-resource-definitions) - we today learned from #instana-ama that having multiple tenant units on Self Hosted Custom Edition is something that is not officially supported by Instana.

We raise request to add this to officially supported features. Customers deciding for a Instana Self Hosted Custom Edition do this for good reasons.

Having the possibility to define multiple tenant units here is a well received critical feature:

• if you need strict separation of data between teams/organizations (which you may can NOT achieve with current RBAC implementation of Instana Groups)

• Scale out load (filler (part of a tenant unit) is well known being scaling bottleneck

• As described in docs already units are great way to separate into organizational domains without the need to setup many Instana Backends

• No need to setup multiple backends if Organization A requires different IdP than Organization B. With tenant units each unit can have it's own IdP config.

• Great way to demo/train/cross sell Instana inside Customers, just create a tmp. Demo/Training Tenant Unit and let Customer teams use this to get familiar with Instana and what it can do without having to install complete backends for this.

• .... sure there are more reasons to be found.

It makes super sense to have this also supported in SHCE - mutlitenancy is in fact a great selling point.