camunda
Mention Risks regarding disabling Multi-Tenancy in Zeebe.
https://camunda.slack.com/archives/CSQ2E3BT4/p1707403002934849
I believe that multitenancy can be disabled at any time (requires restart). Data is not moved. Engine assumes that all requests are for default tenant, so only data in the default tenant are accessible.
Existing process instances for non-default tenant may continue making progress for those tenants, but the related jobs and such are inaccessible to users. For this reason it might not be recommended to do this, unless you've cleared out the cluster (cancelled all instances and deleted processes for all non-default tenants).
If #3347 doesn't cover this issue, we'll need to pull in the Zeebe team for further triage.
How would you decide if it covers it?
Ask the wonderful person who opened the issue! @ManuelDittmar did #3347 cover what you were looking for here? There is a larger follow up topic about "best practices for MT" that hasn't been addressed.