Clarify regional VNet peering limitation for Application Gateway for Containers - #128752
Clarify regional VNet peering limitation for Application Gateway for Containers#128752Fabian (fzankl) wants to merge 1 commit into
Conversation
…Containers
The "Regional VNet Peering" limitation currently reads:
> Application Gateway for Containers deployed in a virtual network in region A and the AKS cluster nodes in a virtual network in region A isn't supported.
Taken literally, this says a deployment in region A with the cluster also in region A is unsupported, which contradicts the rest of the page. The intended statement is that the gateway and the cluster nodes must not be in *different* virtual networks within the same region, matching the FAQ entry further down the page ("Can I deploy Application Gateway for Containers in a separate virtual network from my AKS cluster? A: No.").
This change adds the word "separate" so the bullet reads:
> Application Gateway for Containers deployed in a virtual network in region A and the AKS cluster nodes in a separate virtual network in region A isn't supported.
The wording follows the "Global VNet Peering" bullet directly below it and reuses the term "separate virtual network" already used in the FAQ section of the same article. No technical content changes.
|
Fabian (@fzankl) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Fabian (@fzankl) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 8a96f0b: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Note
Copilot was unable to run its full agentic suite in this review.
Pull request overview
Clarifies the “Regional VNet Peering” limitation wording to avoid implying that same-region/same-VNet deployments are unsupported.
Changes:
- Updates the Regional VNet Peering bullet to specify “separate virtual network” in the same region.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
Bot
added
the
aq-pr-triaged
The "Regional VNet Peering" limitation currently reads:
Taken literally, this says a deployment in region A with the cluster also in region A is unsupported, which contradicts the rest of the page. The intended statement is that the gateway and the cluster nodes must not be in different virtual networks within the same region, matching the FAQ entry further down the page ("Can I deploy Application Gateway for Containers in a separate virtual network from my AKS cluster? A: No.").
This change adds the word "separate" so the bullet reads:
The wording follows the "Global VNet Peering" bullet directly below it and reuses the term "separate virtual network" already used in the FAQ section of the same article. No technical content changes.