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
ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
12
12
---
13
13
# Troubleshoot the AKSCapacityError error code
14
+
---
15
+
title: Troubleshoot the AksCapacityHeavyUsage error code
16
+
description: Discusses how to troubleshoot the AksCapacityHeavyUsage error when you create or start a Kubernetes cluster.
17
+
ms.date: 05/29/2024
18
+
author: axelgMS
19
+
ms.author: axelg
20
+
editor: v-jsitser
21
+
ms.reviewer: chiragpa, anbubin, v-leedennis
22
+
ms.service: azure-kubernetes-service
23
+
ms.topic: troubleshooting-problem-resolution
24
+
ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
25
+
---
26
+
# Troubleshoot the AksCapacityHeavyUsage error code
27
+
28
+
This article discusses how to identify and resolve the `AksCapacityHeavyUsage` error that might occur when you create a Microsoft Azure Kubernetes Service (AKS) cluster.
29
+
30
+
## Symptoms
31
+
32
+
When you try to create an AKS cluster, you receive the following error message:
33
+
34
+
> **Code:** AksCapacityHeavyUsage
35
+
>
36
+
> **Message:** AKS is experiencing heavy usage in region \<Region>. We are working on adding new capacity. In the meantime, please consider creating new AKS clusters in a different region. For a list of all the Azure regions, visit https://aka.ms/aks/regions. For more details on this error, visit https://aka.ms/akscapacityheavyusage.
37
+
38
+
## Cause
39
+
40
+
You're trying to create a cluster in a region that has limited capacity.
41
+
42
+
When you create an AKS cluster, Microsoft Azure allocates compute resources to your subscription. You might occasionally experience the `AksCapacityHeavyUsage` error because of significant growth in demand for Azure Kubernetes Service in specific regions.
43
+
44
+
The `KubernetesAPICallFailed` error message indicates that the AKS cluster didn't start and doesn't have an associated control plane. Therefore, calls to the API server are failing. In this case, you have to retry the Start operation.
45
+
46
+
## Resolution
47
+
48
+
### Solution 1: Select a different region
49
+
50
+
The easiest and quickest solution is to try to deploy to a different region (for example, NorthEurope instead of WestEurope or UAENorth instead of QatarCentral). To find nearby regions, visit the [Azure Geographies page](https://azure.microsoft.com/explore/global-infrastructure/geographies/#overview).
51
+
52
+
This approach might not be feasible if you already have existing resources in the requested region, but it's the preferred solution in a dev/test scenario.
53
+
54
+
### Solution 2: Deploy a cluster that has different settings
55
+
56
+
The infrastructure that hosts AKS-managed clusters have different allocation reservations. Therefore, AKS might have more capacity for public clusters than it has for private clusters. If you experience the `AksCapacityHeavyUsage` error when you try to create a private cluster, try to create a public cluster instead (or vice versa).
57
+
58
+
### Solution 3: Use an Azure Enterprise subscription
59
+
60
+
When capacity is running low, non-Enterprise Agreement (EA) subscriptions are limited first in AKS cluster creation to reserve resources for real production scenarios. If you have an EA subscription, make sure that you use the EA subscription to create the AKS cluster.
61
+
62
+
### Solution 4: Retry the operation
63
+
64
+
Capacity is often reclaimed when other users stop or delete their AKS clusters. Therefore, the operation might succeed if you retry it later.
65
+
66
+
## More information
67
+
68
+
- Ensuring capacity for users is a top priority for Microsoft, and we're working to scale up our infrastructure to accommodate the increasing popularity of Azure services.
69
+
70
+
For more information about improvements that we're making toward delivering a resilient cloud supply chain, see [this September 2021 Azure Blog article](https://azure.microsoft.com/blog/advancing-reliability-through-a-resilient-cloud-supply-chain/).
71
+
72
+
-[General troubleshooting of AKS cluster creation issues](troubleshoot-aks-cluster-creation-issues.md)
73
+
74
+
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
14
75
15
76
This article discusses how to identify and resolve the `AKSCapacityError` error that might occur when you create or start a Microsoft Azure Kubernetes Service (AKS) cluster.
0 commit comments