Skip to content

Commit 873f748

Browse files
authored
Update troubleshoot-app-gateway-ingress-controller-connectivity-issues.md
1 parent 351cb86 commit 873f748

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

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

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -144,15 +144,20 @@ If the `Ingress` lacks an address or displays events that indicate issues, inves
144144

145145
2. **Inspect the logs**:
146146

147-
```console
147+
```console
148148
kubectl logs <INGRESS_POD_NAME> -n <YOUR_NAMESPACE>
149149
```
150+
For the AGIC that is deployed by using the add-on, run the following command:
151+
152+
```console
153+
kubectl logs -n kube-system -l=app=ingress-appgw
154+
```
150155

151156
Look for any errors or warnings that might indicate what's going wrong.
152157

153158
## Step 4: Check Application Gateway operational State
154159

155-
This step 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+
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).
156161

157162
1. **Get the Application Gateway name**:
158163

0 commit comments

Comments
 (0)