We have a small, but significant set of customers who are deploying OSSM with multiple meshes within a single cluster using Maistra's multi-tenant features. We will need to provide a migration path to 3.0 that continues to meet their use cases.

First off, offer guidance on whether multiple control planes are truly needed. In OSSM 2.x, we guided users toward this feature for all "multi-tenant" use cases, even where it might not be truly needed. For cases where traffic isolation is the main requirement, separate control planes are likely not necessary. Separate control planes usually implies separate administrators.

If multiple control planes are not required, guide them to create a separated data plane with a single control plane. This likely needs an issue to cover.

If multiple control planes and data planes are required, we will need to document how Maistra's multi-tenancy compares to what is available with Istio's multi-control plane features, and how users can approximate the same level of permissions and segregation (may involve additional configuration). Related issue: https://issues.redhat.com/browse/OSSM-4025