Merge pull request #270317 from dramasamy/capacity1

[NotReleaseSpecific] Add capacity webhook validation details

Author: prmerger-automator[bot]

articles/operator-nexus/quickstarts-kubernetes-cluster-deployment-arm.md

@@ -45,6 +45,11 @@ Once you have reviewed and saved the template file named ```kubernetes-deploy.js
       --parameters @kubernetes-deploy-parameters.json
 ```
 
+If there isn't enough capacity to deploy requested cluster nodes, an error message appears. However, this message doesn't provide any details about the available capacity. It states that the cluster creation can't proceed due to insufficient capacity.
+
+> [!NOTE]
+> The capacity calculation takes into account the entire platform cluster, rather than being limited to individual racks. Therefore, if an agent pool is created in a zone (where a rack equals a zone) with insufficient capacity, but another zone has enough capacity, the cluster creation continues but will eventually time out. This approach to capacity checking only makes sense if a specific zone isn't specified during the creation of the cluster or agent pool.
+
 ## Review deployed resources
 
 [!INCLUDE [quickstart-review-deployment-cli](./includes/kubernetes-cluster/quickstart-review-deployment-cli.md)]

articles/operator-nexus/quickstarts-kubernetes-cluster-deployment-bicep.md

@@ -42,6 +42,11 @@ Once you have reviewed and saved the template file named ```kubernetes-deploy.bi
       --parameters @kubernetes-deploy-parameters.json
 ```
 
+If there isn't enough capacity to deploy requested cluster nodes, an error message appears. However, this message doesn't provide any details about the available capacity. It states that the cluster creation can't proceed due to insufficient capacity.
+
+> [!NOTE]
+> The capacity calculation takes into account the entire platform cluster, rather than being limited to individual racks. Therefore, if an agent pool is created in a zone (where a rack equals a zone) with insufficient capacity, but another zone has enough capacity, the cluster creation continues but will eventually time out. This approach to capacity checking only makes sense if a specific zone isn't specified during the creation of the cluster or agent pool.
+
 ## Review deployed resources
 
 [!INCLUDE [quickstart-review-deployment-cli](./includes/kubernetes-cluster/quickstart-review-deployment-cli.md)]

articles/operator-nexus/quickstarts-kubernetes-cluster-deployment-cli.md

@@ -99,6 +99,11 @@ az networkcloud kubernetescluster create \
     dns-service-ip="${DNS_SERVICE_IP}"
 ```
 
+If there isn't enough capacity to deploy requested cluster nodes, an error message appears. However, this message doesn't provide any details about the available capacity. It states that the cluster creation can't proceed due to insufficient capacity.
+
+> [!NOTE]
+> The capacity calculation takes into account the entire platform cluster, rather than being limited to individual racks. Therefore, if an agent pool is created in a zone (where a rack equals a zone) with insufficient capacity, but another zone has enough capacity, the cluster creation continues but will eventually time out. This approach to capacity checking only makes sense if a specific zone isn't specified during the creation of the cluster or agent pool.
+
 After a few minutes, the command completes and returns information about the cluster. For more advanced options, see [Quickstart: Deploy an Azure Nexus Kubernetes cluster using Bicep](./quickstarts-kubernetes-cluster-deployment-bicep.md).
 
 ## Review deployed resources

articles/operator-nexus/quickstarts-kubernetes-cluster-deployment-powershell.md

@@ -118,6 +118,11 @@ New-AzNetworkCloudKubernetesCluster -KubernetesClusterName $CLUSTER_NAME `
 -NetworkConfigurationServiceCidr $DNS_SERVICE_IP
 ```
 
+If there isn't enough capacity to deploy requested cluster nodes, an error message appears. However, this message doesn't provide any details about the available capacity. It states that the cluster creation can't proceed due to insufficient capacity.
+
+> [!NOTE]
+> The capacity calculation takes into account the entire platform cluster, rather than being limited to individual racks. Therefore, if an agent pool is created in a zone (where a rack equals a zone) with insufficient capacity, but another zone has enough capacity, the cluster creation continues but will eventually time out. This approach to capacity checking only makes sense if a specific zone isn't specified during the creation of the cluster or agent pool.
+
 After a few minutes, the command completes and returns information about the cluster. For more advanced options, see [Quickstart: Deploy an Azure Nexus Kubernetes cluster using Bicep](./quickstarts-kubernetes-cluster-deployment-bicep.md).
 
 ## Review deployed resources