Allow custom Tenant Prefix

[baswag]

Describe the feature

As a cluster admin, I want to migrate existing Namespaces to be included in a Capsule Tenant, with the forceTenantPrefix enabled.
These namespaces already have a prefix, but that prefix may not be the name of the Tenant.

What would the new user story look like?

1. When a Tenant is created, a custom Tenant prefix can be specified
2. This Prefix is used instead of the Tenant name in admission
3. If no custom prefix is set, it should fall back to the now-current behavior of using the Tenant name
4. If more than one Tenants have defined the same custom prefix, require use of the tenant label for auto-assignment if global forceTenantPrefix is enabled

Expected behavior

Usage of a prefix for tenant namespaces that is not the tenant name.

[Abhishek9639]

Hi @baswag,
I would like to work on this feature request if it’s still open. I went through the proposed behavior and the tenant prefix use case, and I’d be interested in contributing to this enhancement.
Please assign this issue to me.
Thanks!

[baswag]

@Abhishek9639 I already have a working first draft implementation, just wanted to loop in the maintainers on the proposal before opening a PR

[oliverbaehler]

This makes very little sense to me, why aren't you just not forcing the prefix, migrate the existing namespaces, and then enfroce it again.

Why isn't the tenant prefix with how the old namespaces are prefixed?

We are probably not going to accept this feature, as we have to revalidate collisions etc. Something which is already done by the object being present on the Kuberentes API. I would probably invest more time into being able to migrate namespaces between tenants, which is currently not supported.

@prometherion WDTY?