Using kubernetes provider, can't we achieve Blue/Green traffic switch ?

[sathyanarayanan-s]

Description:

I am going through the below documentation for implementing Blue Green Strategy in an assumption that I can do Blue/Green Traffic Switching without L7 tools.

https://docs.flagger.app/tutorials/kubernetes-blue-green

But after spending some efforts in the implementation part, I got to know with kubernetes provider, we cannot do the actual Blue/Green Traffic switch, its just rolling update [in a more automated way after validating SLO and running some tests]

I am thinking that the above link is naming it as "Blue/Green" and the examples given in the documentation is also using kubernetes provider. But its actually doing rolling update for primary pods. Is it not confusing with the naming conventions?

And also I could not find any documentation related to achieve how to achieve Blue/Green using service mesh or ingress.

All I can find is just the below line [which sometime its very hard to understand the complete picture]

route traffic to canary (This doesn't happen when using the kubernetes provider)

Expected behavior

If flagger can handle Blue/Green by using the kubernetes provider may help or Another documentation to achieve the same using service mesh/ingress will help us to understand better.

Additional context

• Flagger version: 1.38.0
• Kubernetes version: 1.30.0
• Service Mesh provider: Nil
• Ingress provider: Nil