Azure AKS集群创建失败求助：PutControlPlane error

Hey there, sorry to hear you're hitting this PutControlPlane error when spinning up your AKS cluster. Let's walk through the most common fixes and checks to get this resolved:

• Verify Resource Group Permissions
  Make sure your Azure account has the right permissions on the upf-infra-ResourceGroup resource group. At minimum, you need the AKS Cluster Contributor or Contributor role. You can check your current assignments with this command:

  az role assignment list --resource-group upf-infra-ResourceGroup --assignee your-azure-email@example.com
  

  If permissions are missing, ask your Azure admin to grant the appropriate role.

• Check Regional Resource Quotas
  AKS requires sufficient compute quotas (like vCPUs) in your target region. If you're hitting a quota limit, the control plane deployment will fail. Run this to check your current vCPU quota:

  az vm list-usage --location your-region-name --query "[?localName=='Total Regional vCPUs']"
  

  If your used quota is close to or at the limit, submit a quota increase request through the Azure Portal.

• Resolve Network Configuration Conflicts
  If there's an existing virtual network or subnet in upf-infra-ResourceGroup, it might be conflicting with AKS's default network setup. Try specifying a custom VNet and subnet explicitly when creating the cluster:

  az aks create --resource-group upf-infra-ResourceGroup --name upf-infra-K8sCluster-1 --node-count 1 --generate-ssh-keys --vnet-subnet-id /subscriptions/your-subscription-id/resourceGroups/upf-infra-ResourceGroup/providers/Microsoft.Network/virtualNetworks/your-vnet-name/subnets/your-subnet-name
  

• Check Azure Service Health
  Temporary outages or degraded service in your region could cause this error. Head to the Azure Portal's Service Health section to check if there are any active issues with the AKS service in your target region.

• Enable Debug Logs for Detailed Insight
  If the above checks don't uncover the issue, re-run the create command with the --debug flag to get verbose logs:

  az aks create --resource-group upf-infra-ResourceGroup --name upf-infra-K8sCluster-1 --node-count 1 --generate-ssh-keys --debug
  

  The debug output will show exactly where the control plane deployment is failing—whether it's a timeout, certificate issue, or something else.

Also, keep that correlation ID d90bed78-075f-4a07-81c0-271dac75e0ca handy. If you reach out to Azure Support, they can use this ID to pull detailed backend logs about the failure.

内容的提问来源于stack exchange，提问作者Raf