Skip to content

Commit 83f415f

Browse files
Merge pull request #234134 from MGoedtel/bug84572
added steps for registering preview flag
2 parents 5d18537 + 3e90786 commit 83f415f

File tree

1 file changed

+40
-6
lines changed

1 file changed

+40
-6
lines changed

articles/aks/use-multiple-node-pools.md

Lines changed: 40 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Use multiple node pools in Azure Kubernetes Service (AKS)
33
description: Learn how to create and manage multiple node pools for a cluster in Azure Kubernetes Service (AKS)
44
ms.topic: article
55
ms.custom: event-tier1-build-2022, ignite-2022, devx-track-azurecli
6-
ms.date: 05/16/2022
6+
ms.date: 03/11/2023
77
---
88

99
# Create and manage multiple node pools for a cluster in Azure Kubernetes Service (AKS)
@@ -406,19 +406,53 @@ It takes a few minutes to delete the nodes and the node pool.
406406

407407
## Associate capacity reservation groups to node pools (preview)
408408

409-
[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
410-
411-
As your application workloads demands, you may associate node pools to capacity reservation groups created prior. This ensures guaranteed capacity is allocated for your node pools.
409+
As your application workloads demands, you may associate node pools to capacity reservation groups already created. This ensures guaranteed capacity is allocated for your node pools.
412410

413411
For more information on the capacity reservation groups, please refer to [Capacity Reservation Groups][capacity-reservation-groups].
414412

415-
Associating a node pool with an existing capacity reservation group can be done using [`az aks nodepool add`][az-aks-nodepool-add] command and specifying a capacity reservation group with the --capacityReservationGroup flag" The capacity reservation group should already exist, otherwise the node pool will be added to the cluster with a warning and no capacity reservation group gets associated.
413+
### Register preview feature
414+
415+
[!INCLUDE [preview features callout](includes/preview/preview-callout.md)]
416+
417+
To install the aks-preview extension, run the following command:
418+
419+
```azurecli
420+
az extension add --name aks-preview
421+
```
422+
423+
Run the following command to update to the latest version of the extension released:
424+
425+
```azurecli
426+
az extension update --name aks-preview
427+
```
428+
429+
Register the `CapacityReservationGroupPreview` feature flag by using the [az feature register][az-feature-register] command, as shown in the following example:
430+
431+
```azurecli-interactive
432+
az feature register --namespace "Microsoft.ContainerService" --name "CapacityReservationGroupPreview"
433+
```
434+
435+
It takes a few minutes for the status to show *Registered*. Verify the registration status by using the [az feature show][az-feature-show] command:
436+
437+
```azurecli-interactive
438+
az feature show --namespace "Microsoft.ContainerService" --name "CapacityReservationGroupPreview"
439+
```
440+
441+
When the status reflects *Registered*, refresh the registration of the *Microsoft.ContainerService* resource provider by using the [az provider register][az-provider-register] command:
442+
443+
```azurecli-interactive
444+
az provider register --namespace Microsoft.ContainerService
445+
```
446+
447+
### Manage capacity reservations
448+
449+
Associating a node pool with an existing capacity reservation group can be done using [`az aks nodepool add`][az-aks-nodepool-add] command and specifying a capacity reservation group with the --capacityReservationGroup flag". The capacity reservation group should already exist, otherwise the node pool will be added to the cluster with a warning and no capacity reservation group gets associated.
416450

417451
```azurecli-interactive
418452
az aks nodepool add -g MyRG --cluster-name MyMC -n myAP --capacityReservationGroup myCRG
419453
```
420454

421-
Associating a system node pool with an existing capacity reservation group can be done using [`az aks create`][az-aks-create] command. If the capacity reservation group specified doesn't exist, then a warning is issued and the cluster gets created without any capacity reservation group association.
455+
Associating a system node pool with an existing capacity reservation group can be done using [`az aks create`][az-aks-create] command. If the capacity reservation group specified doesn't exist, then a warning is issued and the cluster gets created without any capacity reservation group association.
422456

423457
```azurecli-interactive
424458
az aks create -g MyRG --cluster-name MyMC --capacityReservationGroup myCRG

0 commit comments

Comments
 (0)