Multiple Tenants in Same Namespace

[acelinkio]

Is your feature request related to a problem? Please describe.
I would like to have two minio instances created in the same namespace.

Describe the solution you'd like
Allow for multiple Minio tenants to be created in a single namespace.

Describe alternatives you've considered
Workaround creating a namespace per tenant.

Additional context
Looks like this was talked about a few years ago in #922 (comment). Would like to revisit. Think this would be a great UX change and help migrate users from Minio helm chart to this operator.

Right now the only apparent blocker this is one of the names of the Kubernetes service is hardcoded to minio. The others are prefixed with tenantname-console and tenantname-hl.

[ramondeklein]

We won't support multiple MinIO clusters in the same namespace. The hardcoded service name is one thing (but that could be fixed). We prefer separating tenants in their own namespace to keep things simple. With two clusters in a single namespace, it's not clear what belongs to what. Also separating tenants into their own namespace allows for more granular RBAC access.

There are no obvious advantages to combine multiple clusters into a single namespace (IMHO). If you insist on using multiple clusters into a single namespace, then you should deploy your statefulset without operator.

[acelinkio]

I understand the preference for having namespace separation and aiming for simplicity. Is there any documentation covering that and other expectations? Not really finding this operator as intuitive as the others I have worked with.

[ramondeklein]

Good point. I have asked our documentation team to mention that only one object-store per namespace can be deployed.