feat(api): Add forceTenantPrefix option to Tenant spec

[samirtahir91]

This PR adds the option to require the tenant name prefix to it's namespace names, at the tenant level (opposed to setting globally in capsule configuration). With this users do not need to define forceTenantPrefix in capsule configuration if wanting to apply to certain Tenants only.

This allows admins to fine grain which Tenants should be prefixed (i.e. consumer developer teams), whilst giving flexibility on other Tenants like platform team namespaces.

forceTenantPrefix has been added in the Tenant Spec

Requires users to set the capsule.clastix.io/tenant label for Tenants with forceTenantPrefix set to true if more than 1 Tenant matches the owner as well as prefixing the Tenant name in the namespace, or just prefix the namespace with tenant name if matching to a single Tenant with forceTenantPrefix set to true.

[netlify]

✅ Deploy Preview for capsule-documentation canceled.

Name	Link
🔨 Latest commit	9193d36
🔍 Latest deploy log	https://app.netlify.com/sites/capsule-documentation/deploys/673f18ebb7c058000805fe68

[prometherion]

@oliverbaehler what are your thoughts on this?

[oliverbaehler]

I am okay with it, for a new minor release (v0.8.0)

What happens when a tenant has capsule.clastix.io/tenant set to another tenant in both cases. If the option is on tenant basis true or false?

[samirtahir91]

I am okay with it, for a new minor release (v0.8.0)

What happens when a tenant has capsule.clastix.io/tenant set to another tenant in both cases. If the option is on tenant basis true or false?

If I am an owner of the Tenant tenant-a with forceTenantPrefix: true, when I create a namespace with label capsule.clastix.io/tenant: tenant-a and use a invalid prefix, it will be denied as label take presedence and includes the check to see if the labelled Tenant (tenant-a) needs the prefix by looking at the spec.

If tenant-a does not have forceTenantPrefix: true then it would allow the namespace

[oliverbaehler]

Sorry reviewed on my phone bcs im in hospital. I will verify the functionality again when i am on my pc

[samirtahir91]

The test failed for k8s 1.30.0, but unsure why? Can we re-trigger? @oliverbaehler

[oliverbaehler]

#1168 Observed error again https://github.com/projectcapsule/capsule/actions/runs/11666475797/job/32522968722?pr=1244

[samirtahir91]

I'm unsure why, the change was 3 extra test cases which pass with forceTenantPrefix true in Capsule Configuration...

[samirtahir91]

Seems fine now...

[samirtahir91]

@oliverbaehler - could you able to retrigger the failing test pls?