Skip to content

Commit 985ced5

Browse files
authored
Merge pull request #279813 from greg-lindsay/agc-issues
revert #120733
2 parents 19d3ba3 + 0661ec6 commit 985ced5

File tree

3 files changed

+11
-3
lines changed

3 files changed

+11
-3
lines changed

articles/application-gateway/ingress-controller-migration.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: application-gateway
55
author: greg-lindsay
66
ms.service: application-gateway
77
ms.topic: article
8-
ms.date: 07/28/2023
8+
ms.date: 07/01/2024
99
ms.author: greglin
1010
---
1111

@@ -40,6 +40,9 @@ You can now enable the AGIC add-on in your AKS cluster to target your existing A
4040
```azurecli-interactive
4141
az aks enable-addons -n myCluster -g myResourceGroup -a ingress-appgw --appgw-id $appgwId
4242
```
43+
Alternatively, you can navigate to your [AKS cluster in the Azure portal](https://portal.azure.com/?feature.aksagic=true) and enable the AGIC add-on in the **Virtual network integration** tab of your cluster. Select your existing Application Gateway when you choose which Application Gateway that the add-on should target.
44+
45+
![Application Gateway Ingress Controller Portal](./media/tutorial-ingress-controller-add-on-existing/portal-ingress-controller-add-on.png)
4346

4447
## Next Steps
4548
- [**Application Gateway Ingress Controller Troubleshooting**](ingress-controller-troubleshoot.md): Troubleshooting guide for AGIC
Loading

articles/application-gateway/tutorial-ingress-controller-add-on-existing.md

Lines changed: 7 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: application-gateway
77
ms.topic: tutorial
8-
ms.date: 11/28/2023
8+
ms.date: 07/01/2024
99
ms.author: greglin
1010
ms.custom: template-tutorial, devx-track-azurecli
1111
---
@@ -78,9 +78,14 @@ If you'd like to continue using Azure CLI, you can continue to enable the AGIC a
7878
appgwId=$(az network application-gateway show --name myApplicationGateway --resource-group myResourceGroup -o tsv --query "id")
7979
az aks enable-addons --name myCluster --resource-group myResourceGroup --addon ingress-appgw --appgw-id $appgwId
8080
```
81+
## Enable the AGIC add-on in existing AKS cluster through Azure portal
82+
83+
If you'd like to use Azure portal to enable AGIC add-on, go to [(https://aka.ms/azure/portal/aks/agic)](https://aka.ms/azure/portal/aks/agic) and navigate to your AKS cluster through the portal link. Select the **Networking** menu item under **Settings**. From there, go to the **Virtual network integration** tab within your AKS cluster. You'll see an **Application gateway ingress controller** section, which allows you to enable and disable the ingress controller add-on. Select the **Manage** button, then the checkbox next to **Enable ingress controller**. Select the application gateway you created, **myApplicationGateway** and then select **Save**.
84+
85+
:::image type="content" source="./media/tutorial-ingress-controller-add-on-existing/portal-ingress-controller-add-on.png" alt-text="Screenshot showing how to enable application gateway ingress controller from the networking page of the Azure Kubernetes Service.":::
8186

8287
> [!IMPORTANT]
83-
> When you use an application gateway in a different resource group than the AKS cluster resource group, the managed identity **_ingressapplicationgateway-{AKSNAME}_** that is created must have **Network Contributor** and **Reader** roles set in the application gateway resource group.
88+
> If you use an application gateway in a different resource group than the AKS cluster resource group, the managed identity **_ingressapplicationgateway-{AKSNAME}_** that is created must have **Network Contributor** and **Reader** roles set in the application gateway resource group.
8489
8590
## Peer the two virtual networks together
8691

0 commit comments

Comments
 (0)