AKS configuring pod-cidr with portal (not possible)

We can configure pod-cidr on the portal using the following UI is not possible. The configuration below helps to configure service-cidr. What is service cidr? Service cidr is the ip address range used for provisioning of nodes. If you create a new node, then an ip will be assigned to this node. This ip gets it range from service cidr. 

When you create cluster1, the pod cidr is always in the range 10.244.x.x. If you crate another cluster say cluster 2 will also be 10.244.x.x. This won't work if you trying to setup a multimesh like cilium that requires pod address to be unique. 

You can use the following to configure your pod cidr.

az network vnet create \

    --resource-group "${AZURE_RESOURCE_GROUP}" \

    --name "${NAME}-cluster-net" \

    --address-prefixes 192.168.10.0/24 \

    --subnet-name "${NAME}-node-subnet" \

    --subnet-prefix 192.168.10.0/24

# Store the ID of the created subnet

export NODE_SUBNET_ID=$(az network vnet subnet show \

    --resource-group "${AZURE_RESOURCE_GROUP}" \

    --vnet-name "${NAME}-cluster-net" \

    --name "${NAME}-node-subnet" \

    --query id \

    -o tsv)

az aks create \

    --resource-group "${AZURE_RESOURCE_GROUP}" \

    --name "${NAME}" \

    --network-plugin none \

    --pod-cidr "10.10.0.0/16" \

    --service-cidr "10.11.0.0/16" \

    --dns-service-ip "10.11.0.10" \

    --vnet-subnet-id "${NODE_SUBNET_ID}"