Azure Container Apps revisions provide versioned snapshots of an app’s configuration and container template. In multiple-revision mode, traffic can be directed to specific active revisions, enabling controlled rollouts.
Overview and use case
Use Azure Container Apps revisions and traffic weights to roll out a new container version gradually and roll back safely.
Implementation steps
- Enable multiple-revision mode when the release strategy requires multiple active revisions.
- Deploy the new image and wait for the revision to become healthy before assigning production traffic.
- Start with a small traffic weight and monitor latency, error rate, resource use and business signals.
- Increase traffic in stages when the new revision behaves as expected.
- If the release fails, shift traffic back to the previous healthy revision and investigate before retrying.
Example
# List revisions for a Container App
az containerapp revision list \
--name <app-name> --resource-group <resource-group> \
--output table
# Example traffic weights: old revision 90%, new revision 10%
az containerapp ingress traffic set \
--name <app-name> --resource-group <resource-group> \
--revision-weight <old-revision>=90 <new-revision>=10
Common pitfalls
- Do not send traffic to a revision before its readiness and health checks pass.
- Ensure database and message contract changes remain compatible during the overlap period.
- Do not forget to move traffic away from obsolete revisions after a successful rollout.
Testing checklist
Test revision readiness, staged traffic changes, monitoring alerts and rollback under a simulated failure.
Conclusion
Apply the smallest permissions and configuration needed, test both expected and failure paths, and document how the implementation is operated in production.