| title | description | services | author | ms.service | ms.topic | ms.date | ms.author | ms.custom |
|---|---|---|---|---|---|---|---|---|
Application lifecycle management in Azure Container Apps |
Learn about the full application lifecycle in Azure Container Apps |
container-apps |
craigshoemaker |
container-apps |
conceptual |
11/02/2021 |
cshoe |
ignite-fall-2021, event-tier1-build-2022 |
The Azure Container Apps application lifecycle revolves around revisions.
When you deploy a container app, the first revision is automatically created. More revisions are created as containers change, or any adjustments are made to the template section of the configuration.
A container app flows through three phases: deployment, update, and deactivation.
As a container app is deployed, the first revision is automatically created.
:::image type="content" source="media/application-lifecycle-management/azure-container-apps-lifecycle-deployment.png" alt-text="Azure Container Apps: Deployment phase":::
As a container app is updated with a revision scope-change, a new revision is created. You can choose whether to automatically deactivate old revisions, or allow them to remain available.
:::image type="content" source="media/application-lifecycle-management/azure-container-apps-lifecycle-update.png" alt-text="Azure Container Apps: Update phase":::
Once a revision is no longer needed, you can deactivate a revision with the option to reactivate later. During deactivation, containers in the revision are shut down.
:::image type="content" source="media/application-lifecycle-management/azure-container-apps-lifecycle-deactivate.png" alt-text="Azure Container Apps: Deactivation phase":::
The containers are shut down in the following situations:
- As a container app scales in
- As a container app is being deleted
- As a revision is being deactivated
When a shutdown is initiated, the container host sends a SIGTERM message to your container. The code implemented in the container can respond to this operating system-level message to handle termination.
If your application does not respond within 30 seconds to the SIGTERM message, then SIGKILL terminates your container.
[!div class="nextstepaction"] Microservices