MicrosoftDocs
Need add limitation of custom subnet for node pool
[Enter feedback here]
I followed the instructions to create a new node pool and allocate a newly created subnet to it.
My command was "az aks nodepool add -g
However, the error went like "Cannot use a custom subnet because agent nodepool1 is using a managed subnet. Please omit the vnetSubnetID parameter from the request". It means all of my node pools should use the same kind of subnet, managed or custom, not mixed. This limitation was not mentioned in the document, and it affected my work.
Hope this kinda limitation be added into the document to prevent further mistakes.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: 22fbdc3f-fbd1-9cbb-ca03-ad01d145e821
- Version Independent ID: ca927327-0132-f406-52e3-033c6a529245
- Content: Create node pools in Azure Kubernetes Service (AKS) - Azure Kubernetes Service
- Content Source: articles/aks/create-node-pools.md
- Service: azure-kubernetes-service
- Sub-service: aks-nodes
- GitHub Login: @schaffererin
- Microsoft Alias: schaffererin
@mintLiquor Thanks for your feedback! We will investigate and update as appropriate.
Hi, @mintLiquor! Thanks for leaving your feedback here. I've not come across that error and was unable to find any results through search. Could you please share a bit more concrete information so I can try to repro the issue on my end? Thanks!
@schaffererin Sorry for the late response. I was thinking whether I could customize the address space for my node pool, so I added new address space in my vnet, then created a new subnet based on this space. After that, I created a new node pool with "--vnet-subnet-id" of that newly created subnet, and failed. You may follow my steps and give it a try.