I'm currently managing 200 Azure Container Apps and need to set up a Blue/Green deployment strategy. My main challenge is that all 200 apps utilize TCP ingress, but Azure Container Apps doesn't allow traffic splitting or revision labels when TCP is used. I'm looking for ways to ensure a safe, no-downtime deployment for these TCP-based services without the built-in labels. Any advice or alternative strategies would be greatly appreciated!
3 Answers
You might want to check if there's any update in Azure's documentation regarding TCP support. Some people say that traffic splitting is not supported for TCP, but always good to confirm on Azure's own pages for the latest.
Have you considered using health probes? If you're running single revisions, you can set up a health probe to fail the new revision if it doesn't meet the criteria. This way, it won't receive any traffic until it's healthy.
It seems like you'll have to get creative since TCP doesn't support the typical label-based traffic splitting. Have you thought about using Terraform or YAML configurations to create a workaround for your deployments?
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically