Skip to content

Commit bb4d35e

Browse files
authored
Update troubleshoot-app-gateway-ingress-controller-connectivity-issues.md
1 parent 723ec0f commit bb4d35e

File tree

1 file changed

+23
-4
lines changed

1 file changed

+23
-4
lines changed

support/azure/azure-kubernetes/load-bal-ingress-c/troubleshoot-app-gateway-ingress-controller-connectivity-issues.md

Lines changed: 23 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -157,9 +157,11 @@ Look for any errors or warnings that might indicate what's going wrong.
157157

158158
## Step 4: Check Application Gateway operational State
159159

160-
This step only applies to AGIC that is deployed by using the add-on. It focuses on understanding the operational state of the [Application Gateway](/azure/application-gateway/overview) if it's used as an [Ingress Controller on AKS](/azure/application-gateway/ingress-controller-overview).
160+
It focuses on understanding the operational state of the [Application Gateway](/azure/application-gateway/overview) if it's used as an [Ingress Controller on AKS](/azure/application-gateway/ingress-controller-overview).
161161

162-
1. **Get the Application Gateway name**:
162+
### [Add-on](#tab/Add-on)
163+
164+
1. Get the Application Gateway name:
163165

164166
```console
165167
az aks show --name <YOUR_AKS_NAME> --resource-group <YOUR_RG_NAME> --query addonProfiles.ingressApplicationGateway
@@ -180,14 +182,31 @@ This step only applies to AGIC that is deployed by using the add-on. It focuses
180182
}
181183
```
182184

183-
2. **Verify the Application Gateway operational state**:
185+
2. Verify the Application Gateway operational state:
186+
187+
```console
188+
az network application-gateway show --name <YOUR_APPLICATION_GATEWAY_NAME> --resource-group <YOUR_RG_NAME> --query operationalState
189+
```
190+
191+
192+
### [Helm](#tab/helm)
193+
194+
1. Get the Application Gateway name:
195+
196+
```console
197+
helm show values agic-controller --jsonpath "appgw.name"
198+
```
199+
200+
> [!NOTE]
201+
> If you see any unexpected error on this step, you might have misconfigured `AGIC`, see [Install AGIC by using a new Application Gateway deployment](/azure/application-gateway/ingress-controller-install-new).
202+
203+
2. Validate the Application Gateway operational state:
184204

185205
```console
186206
az network application-gateway show --name <YOUR_APPLICATION_GATEWAY_NAME> --resource-group <YOUR_RG_NAME> --query operationalState
187207
```
188208
189209
The expected `operationalState` value is `Running`. If it's something different, you might have to restart the Application Gateway.
190-
191210
## Step 5 (Optional): Inspect Mapped Kubernetes and Application Gateway IPs
192211

193212
The [AGIC](/azure/application-gateway/ingress-controller-overview) monitors the pod IPs and maps them to `backendAddressPools` in the `Application Gateway` instance. This step verifies that integration.

0 commit comments

Comments
 (0)