GetVnetError while creating a new AKS node pool

Question

GetVnetError while creating a new AKS node pool

Wout Ceulemans 0

Command that is used:

`az aks nodepool add -g Quivr_Cluster_group --cluster-name QCluster -n main --node-count 1 --node-vm-size Standard_E4as_v5 --max-pods 200 --mode System --zones 1 --enable-node-public-ip --vnet-subnet-id /subscriptions/

Wout Ceulemans 0 Reputation points

2023-04-12T15:39:56.7133333+00:00

Hello, thanks for the response. We have 2 node pools already using this VNet, and they are working fine. The --vnet-subnet-id is copied & pasted from Azure Portal. This VNet has a AKS-subnet and a database subnet. I have owner permissions of the entire subscription and all resources inside it. Azure Support did recently move our subscription from one owner to another, and the problems started after that. Everything in our cluster is in europe-west. We do not have (or wish to have) resources in any other region.
vipullag-MSFT 26,522 Reputation points Moderator

2023-05-04T04:36:39.4333333+00:00

Hello Wout Ceulemans

Firstly, apologies for the delay in responding here and any inconvenience this issue may have caused.

This issue needs deeper investigation. Support team will be able to check and help on this. I would recommend you to open a azure support case.

If you don't have a support plan enabled on your subscription, I request you to send an email to AzCommunity@Microsoft.com with Subject as "Attn:Vikas" referencing this thread along with your subscription ID. I can then enable your subscription with a one-time free technical support.

Once the issue is resolved, request you to post the resolution here for the benefit of community.

1 answer

Your answer

Wout Ceulemans 0 Reputation points

2023-04-12T15:39:56.7133333+00:00

Hello, thanks for the response. We have 2 node pools already using this VNet, and they are working fine. The --vnet-subnet-id is copied & pasted from Azure Portal. This VNet has a AKS-subnet and a database subnet. I have owner permissions of the entire subscription and all resources inside it. Azure Support did recently move our subscription from one owner to another, and the problems started after that. Everything in our cluster is in europe-west. We do not have (or wish to have) resources in any other region.
vipullag-MSFT 26,522 Reputation points Moderator

2023-05-04T04:36:39.4333333+00:00

Hello Wout Ceulemans

Firstly, apologies for the delay in responding here and any inconvenience this issue may have caused.

This issue needs deeper investigation. Support team will be able to check and help on this. I would recommend you to open a azure support case.

If you don't have a support plan enabled on your subscription, I request you to send an email to AzCommunity@Microsoft.com with Subject as "Attn:Vikas" referencing this thread along with your subscription ID. I can then enable your subscription with a one-time free technical support.

Once the issue is resolved, request you to post the resolution here for the benefit of community.

Answer 1

Hello Wout Ceulemans

Welcome to Microsoft Q&A Platform, thanks for posting your query here.

Based on the information provided, it seems that you encountered a "GetVnetError" while creating a new AKS node pool. The GetVnetError error message typically occurs when there is an issue with the VNet configuration. Some possible reasons for this error include:

The VNet does not exist or is not accessible to your AKS cluster.
The VNet is in a different region or subscription than your AKS cluster.
The VNet is not configured with the necessary subnets to support AKS.

To troubleshoot this issue, you can try the following steps:

Verify that the VNet and subnet specified in the --vnet-subnet-id parameter exist and are accessible to your AKS cluster.
Check that the VNet and subnet are in the same region and subscription as your AKS cluster.
Ensure that the VNet is configured with the necessary subnets for AKS. Specifically, you will need at least one subnet for the AKS cluster and one subnet for the node pool.
Ensure that you have the required permissions to access and modify the VNet and its associated resources. This includes permissions to create and manage subnets, virtual network gateways, and network security groups.

If you continue to experience issues, you may want to try creating a new VNet with the necessary subnets for AKS and then specify that VNet in the --vnet-subnet-id parameter.

Hope this helps.

Share via

GetVnetError while creating a new AKS node pool

1 answer

Your answer