You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running into several problems getting an AKS cluster rolled out using the official example (as of v4.14.0). I will list them here in the order I ran into them:
1. The Kubernetes version 1.19.3 is no longer supported
│ Error: creating Cluster: (Managed Cluster Name "prefix-aks" / Resource Group "aks-resource-group"): containerservice.ManagedClustersClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="AgentPoolK8sVersionNotSupported" Message="Version 1.19.3 is not supported in this region. Please use [az aks get-versions] command to get the supported version list in this region. For more information, please check https://aka.ms/supported-version-list"
To get around this, I changed the version to 1.22.6. This reveals the next problem:
2. IngressApplicationGateway CIDR not contained within virtual network
│ Error: creating Cluster: (Managed Cluster Name "cluster-name" / Resource Group "aks-resource-group"): containerservice.ManagedClustersClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="IngressAppGwAddonConfigInvalidSubnetCIDRNotContainedWithinVirtualNetwork" Message="Subnet Prefix '10.52.1.0/24' specified for IngressApplicationGateway addon is not contained within the AKS Agent Pool's Virtual Network address prefixes '[10.0.0.0/16]'." Target="AddonProfiles.IngressApplicationGateway"
I am not entirely certain what the correct fix is here, but completely commented out this section for now.
That allows me to continue and see the next problem:
3. Service CIDR overlaps with existing Subnets CIDR.
│ Error: creating Cluster: (Managed Cluster Name "cluster-name" / Resource Group "aks-resource-group"): containerservice.ManagedClustersClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="ServiceCidrOverlapExistingSubnetsCidr" Message="The specified service CIDR 10.0.0.0/16 is conflicted with an existing subnet CIDR 10.0.1.0/24" Target="networkProfile.serviceCIDR"
Also discussed here: #57
And there is a PR recommending a fix here: #107
I am running into several problems getting an AKS cluster rolled out using the official example (as of v4.14.0). I will list them here in the order I ran into them:
1. The Kubernetes version
1.19.3
is no longer supportedTo get around this, I changed the version to
1.22.6
. This reveals the next problem:2. IngressApplicationGateway CIDR not contained within virtual network
I am not entirely certain what the correct fix is here, but completely commented out this section for now.
That allows me to continue and see the next problem:
3. Service CIDR overlaps with existing Subnets CIDR.
Also discussed here: #57
And there is a PR recommending a fix here: #107
To get around this I changed to:
The text was updated successfully, but these errors were encountered: