Azure Container Apps includes a built-in revision management system that allows you to track, control, and roll back application updates with ease. Each time you deploy new code or update configuration settings, Azure Container Apps automatically generates a new immutable revision. These revisions enable precise traffic management, safe deployments, blue-green or canary release strategies, and quick rollback in case of failures. By leveraging revision modes, traffic-splitting, and version history, teams can maintain application stability while continuously delivering updates in a controlled and observable manner.
Set revision management to multiple
In the Azure portal, open your container app resource.
On the left side menu, under Application, select Revisions and replicas.
At the top of the Revisions and replicas page, select Choose revision mode.
To switch from single to multi-revision mode, select Confirm.
On the Revisions and replicas page, wait for the Revision Mode setting to update.
The Revision Mode will be set to Multiple after the update. Also, on the left-side menu, the section title changes from Application to Revisions.
Create a new revision with a v2 suffix
In the Azure portal, ensure that you have the Revisions and replicas page of your container app resource open.
- At the top of the page, select + Create new revision.
On the Create and deploy new revision page, complete the following steps:
Name / suffix: Enter v2
- Under Container image, select your container image. aca-az2003.
Select Create.
Wait for the deployment to be completed.
Configure labels on the revisions
On the left-side menu, under Settings, select Ingress.
If Ingress isn't enabled, select Enabled.On the Ingress page, specify the following information:
Ingress traffic: select Accepting traffic from anywhere.
Ingress type: select HTTP.
Client certificate mode: ensure that Ignore is selected.
Transport: ensure that Auto is selected.
Insecure connections: ensure that Allowed is NOT checked.
Target port: enter 5000
IP Security Restrictions Mode: ensure that Allow all traffic is selected.
At the bottom of the Ingress page, select Save, and then wait for the update to complete.
On the left-side menu, under Revisions, select Revisions and replicas.
For the v2 revision, under Label, enter updated
For the other revision, enter current
At the top of the page, select Save.
Configure a traffic percentage on the revisions
Ensure that you have the Revisions and replicas page open.
For the v2 revision, under Traffic, enter 25 as the percentage.
For the other revision, under Traffic, enter 75 as the percentage.
At the top of the page, select Save.
Verify your work
Ensure that you have your Container App open in the Azure portal.
On the left-side menu, under Application, select Revisions and replicas.
Verify that your revisions are configured as follows:
Azure Container Apps uses a revision-based deployment model that creates a new immutable revision each time you update a container app’s configuration or container image. This enables safe, controlled rollouts without disrupting existing traffic. Revisions can be activated, deactivated, or rolled back as needed, allowing teams to test new versions, split traffic for gradual releases, and maintain high availability.
Top comments (0)