<p>I am trying out the minio-operator.</p>
<p>This is a two part question regarding namespaces mentioned in the docs.</p>
<p>I would like have a namespace in which I deploy different kinds of operators.
Eventhough the docs require a dedicated namespace for the operator, I seem to experience no problems so far, putting all my operators in the same namespace.</p>
<blockquote>
<p>The MinIO Operator exists in its own namespace.</p>
</blockquote>
<p>When it comes to tenants the docs also require a dedicated namespace for each tenant.</p>
<blockquote>
<p>When you use the Operator to create a tenant, the tenant must have its own namespace.</p>
</blockquote>
<p>Does this mean nothing else but the tenant can be in this namespace, or just, that no more than one tenant can exist per namespace.
What I would like to do is to put a tenant into the same namespace as the solution, that is consuming the minio API.</p>
<p>Is my attempt wrong, and if so, why?
What is the reason for those constraints?</p>
<p>I could not find any explanation in the <a href="https://min.io/docs/minio/kubernetes/upstream/operations/installation.html" rel="nofollow noreferrer">article</a> I cited above.</p>

<p>Currently, it is not possible to have multiple tenants in the same namespace because the MinIO operator always creates services with the names <code>minio</code>, <code>minio-console</code>, and <code>minio-hl</code> in the installation namespace.</p>
<p>However, a workaround is to use a different namespace for each tenant and use the DNS in Kubernetes to access them: <code>minio.&lt;other-namespace&gt;.svc</code></p>
<p>For more information, refer to <a href="https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/" rel="nofollow noreferrer">https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/</a>.</p>
