Hi flyte team, Is there a supported way to migrate the Flyte data plane from one k8s cluster to another? I know there's a doc on multi-cluster deployments, but I'm wondering if we have a supported path for moving the entirety of a flyte-core deployment from one cluster to the next. I think the biggest question is how to avoid data consistency issues. So keeping S3 / DB separate detached in the new cluster. Bringing up flyteadmin and making sure the endpoints work, and then creating a maintenance window to clear all running jobs, disable access to old flyteadmin, disconnect the S3 / postgres access, and then enable those in the new cluster. Does that sound right?

i think the challenge here is the control plane right? much easier to just move the dataplane.

yep

Bringing up flyteadmin and making sure the endpoints work, and then creating a maintenance window to clear all running jobs, disable access to old flyteadmin, disconnect the S3 / postgres access, and then enable those in the new cluster. Does that sound right?

Would this be a new, clean postgres instance? I think it should be so. Pointing a new flyteadmin to an existing DB would still not give you execution history nor registered workflows in the UI. You can not only bring up flyteadmin and test endpoints but register your workflows and then switch access to the new flyteadmin. Depending on your current registration patterns that at least give you the inventory of workflows in the UI