Merge pull request #302933 from JackStromberg/patch-7

Anycast IP

Author: prmerger-automator[bot]

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

@@ -30,6 +30,9 @@ sections:
       - question: Does Application Gateway for Containers support Kubenet?
         answer: No, Application Gateway for Containers doesn't support Kubenet in favor of [CNI Overlay](/azure/aks/azure-cni-overlay). [Learn more](/azure/aks/upgrade-aks-ipam-and-dataplane) about migrating from Kubenet to CNI Overlay.
 
+      - question: Why does the frontend resolve to an IP address with an ASN location outside the region Application Gateway for Containers is deployed to?
+        answer: Application Gateway for Containers frontends resolve to any anycast IP address. Anycast IP addresses are advertised globally, which may lead to the ASN location being different from Application Gateway for Containers. The resolved location of the IP address is cosmetic and has no bearing on availability or performance in how clients connect.
+
   - name: Performance
     questions:
       - question: How does Application Gateway for Containers support high availability and scalability?
@@ -67,4 +70,4 @@ sections:
         answer: No.  Each ALB controller must use its own unique managed identity.
 
       - question: Can I share the same frontend resource between multiple Gateway and/or Ingress resources in Kubernetes?
-        answer: No. A frontend should be unique to a single Ingress or Gateway resource. Multiple hostnames and routes can be defined in a given Gateway or Ingress resource to eliminate the need for numerous frontend resources.
+        answer: No. A frontend should be unique to a single Ingress or Gateway resource. Multiple hostnames and routes can be defined in a given Gateway or Ingress resource to eliminate the need for numerous frontend resources.