Exam AZ-104 topic 4 question 83 discussion

Answer is WRONG. I assume there is a typo, where it says "updates" it should be "update". az aks nodepool **update** -n pool1 -g RG1 --cluster-name cluster1 **max-surge 2** https://learn.microsoft.com/en-us/cli/azure/aks/nodepool?view=azure-cli-latest We want to edit an existing node pool, so we cannot use "add": "Add a node pool to the managed Kubernetes cluster." We want to update the properties of the node pool, so we need to use: az aks nodepool update "Update a node pool properties." We want to set it up to use more nodes during an update, so this one is right: --max-surge "Extra nodes used to speed upgrade. When specified, it represents the number or percent used, eg. 5 or 33%."

Based on document, it is Box 1: Update Box 2: --max-surge I'm very new here, and I could be wrong. Here is the link. Please verify and don't take my word for it. https://learn.microsoft.com/en-us/azure/aks/upgrade-cluster?tabs=azure-cli

max-surge allows AKS to temporarily add nodes for an upgrade without manually scaling the node pool up and down.

WRONG update --max-surge 2

az aks upgrade --resource-group myResourceGroup --name myAKSCluster --max-surge 2 upgrade max-surge 2

- add - -node-count 2

https://learn.microsoft.com/en-us/azure/aks/upgrade-aks-cluster?tabs=azure-cli#customize-node-surge-upgrade # Set max surge for a new node pool az aks nodepool add -n mynodepool -g MyResourceGroup --cluster-name MyManagedCluster --max-surge 33% # Update max surge for an existing node pool az aks nodepool update -n mynodepool -g MyResourceGroup --cluster-name MyManagedCluster --max-surge 5

az aks nodepool add --name pool1 --resource-group RG1 --cluster-name cluster1 --node-count 2 This is what I would use to deploy two new nodes in the cluster, which is the first requirement. Then I would run az aks upgrade --resource-group RG1 --name cluster1 --kubernetes-version XX to actually upgrade the cluster. I can't test this unfortunately but it makes the most sense to me.

az: This is the Azure CLI command-line tool. aks: This part of the command is specific to the Azure Kubernetes Service (AKS) features. nodepool update: This is the action being performed, which is updating the properties of an AKS node pool. -n pool1: Specifies the name of the node pool (pool1) that you want to update. Replace pool1 with the actual name of your node pool. -g rg1: Specifies the resource group (rg1) where your AKS cluster is located. Replace rg1 with the actual name of your resource group. --cluster-name cluster1: Specifies the name of the AKS cluster (cluster1) to which the node pool belongs. Replace cluster1 with the actual name of your AKS cluster. --max-surge=2: Specifies the maximum number of nodes that can be added to the node pool at the same time during an upgrade. In this example, it sets the maximum surge to 2. Replace 2 with the desired value. This command allows you to update various properties of an AKS node pool, and in this case, it specifically sets the maximum surge during an upgrade. The "max surge" is relevant when you perform a node pool upgrade, allowing you to control the number of additional nodes that can be added at once during the upgrade process.

update and max-surge

Add an ARM64 node pool into your existing cluster using the az aks nodepool add. az aks nodepool add \ --resource-group myResourceGroup \ --cluster-name myAKSCluster \ --name armpool \ --node-count 3 \ --node-vm-size Standard_D2pds_v5

https://learn.microsoft.com/en-us/azure/aks/upgrade-cluster?tabs=azure-cli#set-max-surge-values Key word existing

on exam 31/Jul/2023.

Box 1: add az aks nodepool add Add a node pool to the managed Kubernetes cluster. Box 2: --max-surge 2 Extra nodes used to speed upgrade. When specified, it represents the number or percent used, eg. 5 or 33%. Incorrect: * --max-count 2 Maximum nodes count used for autoscaler, when "--enable-cluster-autoscaler" specified. Please specify the value in the range of [0, 1000] for user nodepool, and [1,1000] for system nodepool. However, autoscaler not mention in the question. * --max-pods -m The maximum number of pods deployable to a node. * --node-count -c Number of nodes in the Kubernetes agent pool. After creating a cluster, you can change the size of its node pool with az aks scale. default value: 3 Reference: https://learn.microsoft.com/en-us/cli/azure/aks/nodepool

Updates + MAX Surge!!

Agree with others for update. I don't believe it's scale since this is referring to low resource as per below; https://learn.microsoft.com/en-us/azure/aks/scale-cluster?tabs=azure-cli And the question doesn't mention the need for a new pool, since we need to minimise costs and use existing pool to to do so, I'd have to presume to use existing so; 1: Update 2: Max surge See: https://learn.microsoft.com/en-us/azure/aks/upgrade-cluster?tabs=azure-cli#upgrade-an-aks-cluster

It's already existing cluster, So "update" an "max-surge 2" is fit in...