Is it possible to disable or ignore the trafficRouting?

[awx-fuyuanchu]

Argo Rollouts is an awesome tool we have adopted in our canary release workflow. It works well for normal services. However, we are also working on a project that builds the canary release for our API gateway.

Currently, the issue is that we use the GCP global external load balancer to distribute the requests to the API gateways running on multiple Kubernetes clusters. The Gateway API plugin works fine if the backend of the load balancer is on a single cluster. But for this special case, the backends are running in multiple clusters, which makes it impossible to work with the Gateway API plugin.

So the idea is that we use the Argo Rollouts as the cluster-level canary orchestrator. In each cluster, the Argo Rollouts is responsible for managing the ReplicaSets, the stable service, and the canary service. Then, we'll implement a central control plane to update the traffic weight on the load balancer.

So, the central control plane will

1. Tell the Argo Rollouts on all clusters to start a canary. The Canary service will point to the Canary replicas.
2. Update the weight to route canary traffic to the canary services on all clusters progressively.
3. Tell the Argo Rolloutson all clusters to finalize the canary. The Canary service will point to the Stable replicas.

[kostis-codefresh]

Please check the discussion on the other issues linked here https://argo-rollouts.readthedocs.io/en/stable/best-practices/#understand-the-scope-of-argo-rollouts

Basically what you are describing is outside the scope of Argo Rollouts. What you want to do can be another controller or a separate project.

[gourav3010]

There is Workaround possible for this scenerio where you can use SMI feature where Your Argo Rollout will create trafficsplit Custom Resource. You can write your own controller which will reconciles this weight info from the trafficsplit CR and set it onto your loadbalancer layer.