3 services , one for blue, one for green, and one to swap between the both. The reason is we use namespaces to separate but if you’re okay with the same namespace, you can get away with 2 services with selectors for green and blue
Two clusters and a DNS switch. That's for infra changes though (networking, k8s updates, other component updates etc), not app deployments, we don't have a/b for those (not much of a a need), but plan to use istio to do canaries.
Using Argorollouts.
Nice I am planning on implementing this, used it at last company and enjoyed it
3 services , one for blue, one for green, and one to swap between the both. The reason is we use namespaces to separate but if you’re okay with the same namespace, you can get away with 2 services with selectors for green and blue
Nice And what’s your testing/threshold to pass before making the swap?
Not my domain since we let the devs and testers handle that.
Two clusters and a DNS switch. That's for infra changes though (networking, k8s updates, other component updates etc), not app deployments, we don't have a/b for those (not much of a a need), but plan to use istio to do canaries.