Skip to content

Commit facc10d

Browse files
authored
Merge pull request #285987 from MicrosoftDocs/main
9/2/2024 PM Publish
2 parents 84de0be + d9439fd commit facc10d

22 files changed

+564
-158
lines changed

articles/application-gateway/application-gateway-faq.yml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -570,6 +570,12 @@ sections:
570570
To satisfy this `Ingress` resource, an ingress controller is required, which listens for any changes to `Ingress` resources and configures the load balancer policies.
571571
572572
The Application Gateway Ingress Controller (AGIC) allows [Application Gateway](https://azure.microsoft.com/services/application-gateway/) to be used as the ingress for an [Azure Kubernetes Service](https://azure.microsoft.com/services/kubernetes-service/), also known as an AKS cluster.
573+
574+
- question: Can I configure Application Gateway directly instead of using ingress controller?
575+
answer: |
576+
Direct configuration of Application Gateway isn't supported.
577+
578+
If there is a need to change settings on Application Gateway, make the change by using the exposed configuration on the ingress controller or other Kubernetes objects, such as by using supported annotations. After an Application Gateway is linked to Application Gateway Ingress Controller (AGIC), nearly all configuration of that gateway will be synced and controlled by the ingress controller. If you're trying to directly configure Application Gateway imperatively or through infrastructure as code, those changes will eventually be overwritten by the ingress controller.
573579
574580
- question: Can a single ingress controller instance manage multiple application gateways?
575581
answer: Currently, one instance of an ingress controller can only be associated to one application gateway.

0 commit comments

Comments
 (0)