Skip to content

Add validation for AGIC subnet configuration #5832

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rahulrai-in wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Add validation for AGIC subnet configuration #5832

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
b6f032a
Add validation for AGIC subnet configuration
rahulrai-in Jun 19, 2026
00fb06c
Potential fix for pull request finding
rahulrai-in Jun 19, 2026
1f7afec
Potential fix for pull request finding
rahulrai-in Jun 22, 2026
e240845
Potential fix for pull request finding
rahulrai-in Jun 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,7 @@ Monitor the release status by regions at [AKS-Release-Tracker](https://releases.
* AKS now allows migration from the `managedNATGatewayV2` outbound type to the `block` and `none` outbound types, supporting [network-isolated cluster](https://learn.microsoft.com/azure/aks/concepts-network-isolated) scenarios. Migration to other outbound types remains blocked.
* AKS now validates pod CIDR ranges during cluster create and update for kubenet and [Azure CNI Overlay](https://learn.microsoft.com/azure/aks/azure-cni-overlay) clusters. Clusters can no longer be created or updated with a pod CIDR that overlaps with reserved IP ranges (`172.30.0.0/16`, `172.31.0.0/16`), preventing potential in-cluster networking failures. Existing clusters with an overlapping pod CIDR are unaffected. See [CNI prerequisites](https://learn.microsoft.com/azure/aks/concepts-network-cni-overview#prerequisites).
* AKS now rejects [Calico NPM and Azure NPM](https://learn.microsoft.com/azure/aks/use-network-policies) install and uninstall operations on clusters running Kubernetes versions earlier than 1.30. Requests are rejected at the API level with a descriptive error directing customers to upgrade to a newer supported Kubernetes version before retrying. Existing clusters already using Calico NPM or Azure NPM are unaffected.
* AKS now blocks the [Application Gateway Ingress Controller (AGIC)](https://learn.microsoft.com/azure/application-gateway/ingress-controller-overview) add-on from using the AKS-managed `aks-appgateway` subnet. This subnet is reserved for [Application Gateway for Containers (AGC)](https://learn.microsoft.com/azure/application-gateway/for-containers) and can't be used by AGIC due to subnet delegation constraints. Requests using this configuration now fail validation. Use a dedicated subnet by specifying `--appgw-subnet-id` (or `--appgw-subnet-cidr` during cluster create).

#### Bug fixes

Expand Down
Loading