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
Copy file name to clipboardExpand all lines: scenarios/azure-compute-docs/articles/virtual-machine-scale-sets/tutorial-modify-scale-sets-cli.md
+5-8Lines changed: 5 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -15,18 +15,13 @@ Throughout the lifecycle of your applications, you may need to modify or update
15
15
16
16
Below, we declare environment variables that will be used throughout this document. A random suffix is appended to resource names that need to be unique for each deployment. The `REGION` is set to *WestUS2*.
az group create --name $MY_RESOURCE_GROUP_NAME --location $REGION
31
26
```
32
27
@@ -49,6 +44,7 @@ az group create --name $MY_RESOURCE_GROUP_NAME --location $REGION
49
44
To ensure that subsequent update and query commands have a valid resource to work on, create a Virtual Machine Scale Set. In this step, we deploy a basic scale set using a valid image (*Ubuntu2204*) and set the instance count to 5 so that instance-specific updates can target an existing instance ID.
50
45
51
46
```azurecli-interactive
47
+
export SCALE_SET_NAME="myScaleSet$RANDOM_SUFFIX"
52
48
az vmss create \
53
49
--resource-group $MY_RESOURCE_GROUP_NAME \
54
50
--name $SCALE_SET_NAME \
@@ -319,6 +315,7 @@ Running [az vm show](/cli/azure/vm#az-vm-show) again, we now will see that the V
319
315
There are times where you might want to add a new VM to your scale set but want different configuration options than those listed in the scale set model. VMs can be added to a scale set during creation by using the [az vm create](/cli/azure/vmss#az-vmss-create) command and specifying the scale set name you want the instance added to.
Copy file name to clipboardExpand all lines: scenarios/azure-management-docs/articles/azure-linux/tutorial-azure-linux-add-nodepool.md
-2Lines changed: 0 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -64,8 +64,6 @@ az aks nodepool add \
64
64
To see the status of your node pools, use the `az aks nodepool list` command and specify your resource group and cluster name. The same environment variable values declared earlier are used here.
65
65
66
66
```azurecli-interactive
67
-
export CLUSTER_NAME="myAKSClusterabcf37"
68
-
export RESOURCE_GROUP="myAKSResourceGroupabcf37"
69
67
az aks nodepool list --resource-group $RESOURCE_GROUP --cluster-name $CLUSTER_NAME
az group create --name $RESOURCE_GROUP_NAME --location $REGION
45
43
```
@@ -64,10 +62,9 @@ az group create --name $RESOURCE_GROUP_NAME --location $REGION
64
62
65
63
## Create an Azure Linux Container Host cluster
66
64
67
-
Create an AKS cluster using the `az aks create` command with the `--os-sku` parameter to provision the Azure Linux Container Host with an Azure Linux image. The following example creates an Azure Linux Container Host cluster. A unique cluster name is generated using the same RANDOM_SUFFIX used when creating the resource group.
65
+
Create an AKS cluster using the `az aks create` command with the `--os-sku` parameter to provision the Azure Linux Container Host with an Azure Linux image. The following example creates an Azure Linux Container Host cluster.
Copy file name to clipboardExpand all lines: scenarios/azure-management-docs/articles/azure-linux/tutorial-azure-linux-telemetry-monitor.md
-9Lines changed: 0 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -26,15 +26,6 @@ In the next and last tutorial, you'll learn how to upgrade your Azure Linux node
26
26
- If you're connecting an existing AKS cluster to a Log Analytics workspace in another subscription, the Microsoft.ContainerService resource provider must be registered in the subscription with the Log Analytics workspace. For more information, see [Register resource provider](/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider).
27
27
- You need the latest version of Azure CLI. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI](/cli/azure/install-azure-cli).
28
28
29
-
## Environment Variables
30
-
31
-
To ensure unique resource names for each deployment, we declare the following environment variables. These variables will be used throughout the tutorial.
0 commit comments