Open luisdavim opened 2 years ago
I'm in the same boat. Stefan Prodan and I had a chat about that in the CNCF #flagger slack channel:
Since we don't need a service mesh in our infrastructure, we decided not introduce one to keep it simple. Having to introduce a service mesh solely to support this traffic shift seems to be overkill for our purpose. It would be great if Flagger can support this feature.
Describe the feature
Currently, when using the kubernetes provider to do blue/green deployments, the traffic is not shifted to the canary whilst the rollout happens in the primary, that means that we get a regular rolling upgrade once the canary version is validated and the traffic is not shifted from one version and users may be served from a mix of the two versions
Proposed solution
Flagger is capable of patching the selector in the service resources, can't that be used to shift the traffic to the canary whilst the rollout happens in the primary, like it's done with the other providers?