Skip to content

Commit a45b5a6

Browse files
Merge pull request #313085 from JackStromberg/patch-50
affect of maintenance
2 parents 14fddf9 + f9bce71 commit a45b5a6

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

articles/application-gateway/for-containers/scaling-zone-resiliency.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: mbender-ms
66
ms.custom: references_regions
77
ms.service: azure-appgw-for-containers
88
ms.topic: concept-article
9-
ms.date: 05/09/2024
9+
ms.date: 3/12/2026
1010
ms.author: mbender
1111
# Customer intent: As an application architect, I want to configure autoscaling for the Application Gateway for Containers, so that I can ensure high availability and performance while optimizing costs based on traffic demands.
1212
---
@@ -25,7 +25,7 @@ Azure Application Gateway for Containers is always deployed in a highly availabl
2525

2626
## Maintenance
2727

28-
Updates initiated to Application Gateway for Containers are applied one update domain at a time to eliminate downtime. During maintenance, operation and configuration updates continue to be applied. Active connections are gracefully drained for up to 5 minutes, establishing new connections to the remaining capacity in a different update domain prior to the update beginning. During update, Application Gateway for Containers temporarily runs at a reduced maximum capacity. The update process proceeds through each update domain, only proceeding to the next update domain once a healthy status is returned.
28+
Updates initiated to Application Gateway for Containers are applied one update domain at a time to eliminate downtime. During maintenance, operation and configuration updates continue to be applied. Active connections are gracefully drained for up to 5 minutes, establishing new connections to the remaining capacity in a different update domain prior to the update beginning. The update process proceeds through each update domain, only proceeding to the next update domain once a healthy status is returned.
2929

3030
## Next steps
3131

0 commit comments

Comments
 (0)