This message was deleted.

Last two jobs we did a blue green style for making cluster changes. Neither was GKE but I don't think that changes much.

Yeah, we will move to do same for our AKS and EKS as well just starting with GKE at first. Wanted to see if this is right approach. And we use argoCD for deployments which I think will be bottle neck as every time we create a new GKE, means we have to update kube endpoint in ArgoCD.

we’re building a flow for this at prodvana.io

We do blue-green in EKS and use ArgoCD application sets with clusterGenerator so our ArgoApps have labels and the Argo clusters have labels and it installs to the matching clusters. So if we spin up a new cluster we can add a cluster w/ a label to ArgoCD and all applications suddenly install correctly and are 1:1 on both clusters

This sounds interesting @Andre Marcelo-Tanner Let me check on this and is it fine if I reach out to you personally to talk further on this if required?

im interested in the same type of argo setup, if you dont mind continuing to share in thread 😄

Great, so two people with same issues.. can brainstorm on this.

Yes pls feel free to PM more questions about blue/green I would say the hardest part if how you transition traffic and work from one cluster to another. We ended up using AWS global accelerator but you can use DNS weights also or some other L7 service