You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bug report -> please search issues before submitting
documentation issue or request
regression (a behavior that used to work and stopped in a new release)
Issue description
I'm trying to implement a blue/green deployment pattern and would love to know if you have any recommendations. I have multiple container apps and an Application Gateway
What I have considered so far:
Using ingress traffic and label weights
The thought here is that each container app has a green and a blue label on its revisions, and their ingresses decides which revision gets traffic
It's more complex to switch each container one by one
Can't switch the whole system between blue and green at once
Using two container app environments
The thought here is to have a blue and a green container app environment. Each service with external endpoints will have two backend pools that the app gw can switch between.
Pros
The whole system is either blue or green
Network settings (and other settings that has more to do with the container app rather than a revision in it) can be changed without affecting production
Cons
Possibly lots of backend pools
Not possible to do canary/gradual deployments
Using something between app gw and cae
If we stick to having two container app environments, we might put something between them whose job it is to route traffic to either blue or green environment. Something like nginx or ocelot
Pros
The same benefits as the previous solution as it builds on the same idea
Good control over traffic - possible to do canary deployments
Cons
Setting up and maintaining another service
Cost of having another service
Conclusion
There might be other possibilities that I haven't even considered - do you have any ideas or suggestions?
Do you have any general recommendations?
The text was updated successfully, but these errors were encountered:
This issue is a: (mark with an x)
Issue description
I'm trying to implement a blue/green deployment pattern and would love to know if you have any recommendations. I have multiple container apps and an Application Gateway
What I have considered so far:
Using ingress traffic and label weights
The thought here is that each container app has a green and a blue label on its revisions, and their ingresses decides which revision gets traffic
Pros
Cons
Using two container app environments
The thought here is to have a blue and a green container app environment. Each service with external endpoints will have two backend pools that the app gw can switch between.
Pros
Cons
Using something between app gw and cae
If we stick to having two container app environments, we might put something between them whose job it is to route traffic to either blue or green environment. Something like nginx or ocelot
Pros
Cons
Conclusion
There might be other possibilities that I haven't even considered - do you have any ideas or suggestions?
Do you have any general recommendations?
The text was updated successfully, but these errors were encountered: