Hotspot Question You have an Azure subscription that contains an Azure Kubernetes Service (AKS) cluster named Cluster1. Cluster1 hosts a node pool named Pool1 that has four nodes. You need to…

Question

Exhibit

Answer Area

• az aks nodepoolupdates
  addget-updatesscaleupdates
• -n pool1 -g RG1 --cluster-name cluster1--max-surge 2
  --max-count 2--max-pods 2--max-surge 2--node-count 2

Explanation

To perform a coordinated upgrade of an AKS node pool while deploying two temporary new nodes and minimizing costs, the correct interaction is to select 'updates' and '--max-surge 2' in the az aks nodepool command.

Approach. The question asks to perform a 'coordinated upgrade' of an AKS cluster's node pool, specifically to 'deploy two new nodes to perform the upgrade' and 'minimize costs'.

1. First dropdown selection: 'updates': The az aks nodepool update (or updates as presented in the option list) command is used to modify the properties or settings of an existing node pool, which includes configuring its upgrade strategy, such as surge. This command is the correct choice for setting up how the upgrade will proceed, addressing the 'coordinated upgrade' requirement.

2. Second dropdown selection: '--max-surge 2': The --max-surge parameter is used with the az aks nodepool update command to define the number of additional nodes that Azure Kubernetes Service (AKS) can temporarily provision during an upgrade. Setting --max-surge 2 ensures that two extra nodes are temporarily added to the node pool during the upgrade process. This allows the cluster to maintain capacity and high availability while older nodes are upgraded, fulfilling the requirement to 'deploy two new nodes' for the upgrade. Since these nodes are temporary and de-provisioned after the upgrade, this approach also helps to 'minimize costs' compared to permanently expanding the cluster.

Common mistakes.

• common_mistake. 1. Selecting 'scale' instead of 'updates': The az aks nodepool scale command is used to permanently change the number of nodes in a node pool. Using 'scale' would permanently increase the number of nodes, leading to continuous higher costs, which contradicts the 'minimize costs' requirement for a temporary upgrade surge.

1. Selecting '--node-count 2': This parameter is used to set the permanent desired node count for a node pool. If applied in this context, it would change the node pool's permanent size. Given the node pool already has four nodes, setting --node-count 2 would shrink the node pool, which is not what is required for an upgrade that needs additional temporary nodes.
2. Selecting '--max-count 2' or '--max-pods 2': These parameters are not relevant for defining the surge behavior during an AKS node pool upgrade. --max-pods controls the maximum number of pods that can run on a single node, and --max-count is not a standard parameter for configuring upgrade surge.

Concept tested. Azure Kubernetes Service (AKS) node pool upgrade strategies, specifically the use of 'max surge' to perform rolling upgrades with temporary additional nodes for high availability and cost optimization during the upgrade process.

Reference. https://learn.microsoft.com/en-us/azure/aks/upgrade-cluster?tabs=azure-cli#customize-node-surge-upgrade

No community discussion yet for this question.