Centralized Rollout for multi-cluster environments

[edubonifs]

Summary

I think it could be really good if we could create a centralized rollout that would be deployed in several workload clusters.

Use Cases

At this moment, if we want to schedule a rollout in multiple clusters at the same time, in a multi-cluster environment, we only have the possibility of creating a different rollout object for each remote cluster and promote them one by one.

It would be really would to have a centralized rollout which would be deployed to remote clusters, and when you promote this centralized rollout, all workload rollouts would promote at the same time.

This would cover a lot of use cases of Istio community willing to deploy canary deployment in a multi-cluster environment.

All rollouts would be configured the same and will take prometheus metrics from the same source of truth, so it will be a way of deploying new versions of the application at the same time based on prometheus queries.

Message from the maintainers:

Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.

[edubonifs]

This would also solve already open issues as this one: https://github.com/argoproj/argo-rollouts/issues/2088

[zachaller]

I think a syncing step plugin would be the way to implement this.

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity.

[tinkerborg]

This type of functionality can be achieved using something like Karmada (I am not affiliated with the project, I'm just someone looking to solve the same problem). Some interesting viewing here.