Skip to content

Commit ec7ceb6

Browse files
Update ingress-controller-disable-addon.md
1 parent f17d28b commit ec7ceb6

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/application-gateway/ingress-controller-disable-addon.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: application-gateway
55
author: greg-lindsay
66
ms.service: azure-application-gateway
77
ms.topic: how-to
8-
ms.date: 9/17/2024
8+
ms.date: 2/28/2025
99
ms.author: greglin
1010
---
1111

@@ -16,7 +16,7 @@ When you deploy the Application Gateway Ingress Controller (AGIC) as an Azure Ku
1616
The life cycle of the Azure Application Gateway deployment differs when you disable the AGIC add-on, depending on whether you created the Application Gateway deployment by using the AGIC add-on or you deployed it separately from the add-on. You can run the same command to re-enable the AGIC add-on if you ever disable it, or to enable the AGIC add-on by using an existing AKS cluster and Application Gateway deployment.
1717

1818
> [!TIP]
19-
> Consider [Application Gateway for Containers](for-containers/overview.md) for your Kubernetes ingress solution.
19+
> Consider [Application Gateway for Containers](for-containers/overview.md) for your Kubernetes ingress solution. For more information, see [Quickstart: Deploy Application Gateway for Containers ALB Controller](for-containers/quickstart-deploy-application-gateway-for-containers-alb-controller.md).
2020
2121
## Disable the AGIC add-on with an associated Application Gateway deployment
2222

0 commit comments

Comments
 (0)