Hosting separate instances of your software in the same Kubernetes cluster is challenging
Most service providers choose namespaces to isolate their tenants since separate clusters would be too expensive but namespaces provide a very weak level of isolation.
Whether upgrading single tenants or even patching the underlying cluster, any of these changes are hard to manage in a multi-tenant Kubernetes cluster. Separate control planes with Loft can fix this.
If one tenants needs a certain version of a cluster-wide component or a Kubernetes CRD than another one, you will quickly be hitting the limits of namespace-based Kubernetes multi-tenancy.