Update tutorial-ingress-controller-add-on-new.md #92253
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Release [2022-02-24](https://github.com/Azure/AKS/releases/tag/2022-02-24) changed the default VNET configuration: > The default VNET address for managed VNETs will change from 10.0.0.0/8 to 10.224.0.0/12 and the default node subnet address will change from 10.240.0.0/16 to 10.224.0.0/16. New clusters will be required to have service and pod CIDR ranges that do not overlap with these new VNET ranges. Running the the suggested command will output the following error: ``` $ az aks create -n myCluster -g myResourceGroup --network-plugin azure --enable-managed-identity -a ingress-appgw --appgw-name myApplicationGateway --appgw-subnet-cidr "10.2.0.0/16" --generate-ssh-keys (IngressAppGwAddonConfigInvalidSubnetCIDRNotContainedWithinVirtualNetwork) Subnet Prefix '10.2.0.0/16' specified for IngressApplicationGateway addon is not contained within the AKS Agent Pool's Virtual Network address prefixes '[10.224.0.0/12]'. Code: IngressAppGwAddonConfigInvalidSubnetCIDRNotContainedWithinVirtualNetwork Message: Subnet Prefix '10.2.0.0/16' specified for IngressApplicationGateway addon is not contained within the AKS Agent Pool's Virtual Network address prefixes '[10.224.0.0/12]'. Target: AddonProfiles.IngressApplicationGateway ``` I'm suggesting the following changes in this article: - Ingress AGW IP example range: `10.225.0.0/16` - Add info and reference to the the newly introduced requirements.
Contributor
Merged
3 tasks
Contributor
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #label:"aq-pr-triaged" |
Contributor
|
The live article has been substantially updated since this PR was submitted. The changes are no longer applicable. I'll close the PR now. Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release 2022-02-24 changed the default VNET configuration:
Running the the suggested command will output the following error:
I'm suggesting the following changes in this article:
10.225.0.0/16