Closed torumakabe closed 2 years ago
@ToruMakabe Thank you for your query . We will investigate and update the thread.
@ToruMakabe Azure Application Gateway V2 SKU is always deployed in a way that will maintain high availability (requiring 2 instances), even if the instance count is manually configured to 1. This is stated (indirectly) on the Application Gateway V2 SKU autoscaling & high availability section.
@TravisCragg-MSFT Thanks. I got the background. The followings are my requests to the doc.
@ToruMakabe Thank you for outlining what to add to the docs! I have assigned the issue to the content author to evaluate and update as appropriate.
v2 overview and autoscaling info split out.
Let me check the IP address used to communicate with the backend pool.
According to this doc, If the backend pool contains an internally resolvable FQDN or a private IP address, the application gateway routes the request to the backend server by using its instance private IP addresses.
Also, another article says like this, "Application Gateway uses one private IP address per instance, plus another private IP address if a private front-end IP is configured."
But, it seems that App GW uses IP addresses over the number of instances in my env.
An overview of my environment
[Clients]---[Public IP]---[App GW (1 instance)]---[Internal Azure Load Balancer]---[NGINX on AKS pods]
Configuration
Logs of NGINX
The number of App GW instances is 1. But it seems coming from 2 IP addresses (10.0.48.5 and 10.0.48.6). Is this the correct behavior? Is it consistent with the document?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.