Switching traffic from one Kubernetes cluster to other one

[JatinSanghvi]

I have two Kubernetes clusters, each one with AGIC installed and pointing to the same Azure Application Gateway instance. There is an ingress resource created on cluster 1 and now I want to divert all traffic for the same HTTP request URL to cluster 2. How do I achieve it without the two AGICs overriding each other's settings in the Application Gateway and without any downtime?

For example, if I try deleting ingress resource from cluster 1, give some time for the change to be reflected on the Application Gateway, and then after create ingress on cluster 2, there will be a few minutes of downtime. If I instead create an ingress first on cluster 2, and later delete the old ingress on cluster 1, I guess this might lead to one AGIC messing up the configuration changes made by other AGIC. I haven't tested the behavior yet. An ideal way to handle this would be to add a new backend targets to the same backend pool, and then remove the old targets, when old ingress resource is deleted.

Please let me know if this a supported scenario and if so, what should be the sequence of steps to reroute the incoming traffic. Thanks.

PS: The question is similar to one in #1470 but it is unanswered yet and seems to highlight an issue where the Application Gateway settings are getting deleted.