Skip to content

Commit 30d7205

Browse files
author
naman-msft
committed
added a bunch of new converted docs and updated their metadata to be still compliant with prod metadata
1 parent 42bf42d commit 30d7205

File tree

5 files changed

+447
-23
lines changed

5 files changed

+447
-23
lines changed

scenarios/azure-compute-docs/articles/virtual-machine-scale-sets/tutorial-modify-scale-sets-cli.md

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -15,18 +15,13 @@ Throughout the lifecycle of your applications, you may need to modify or update
1515

1616
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*.
1717

18-
```bash
19-
export RANDOM_SUFFIX=adcc95
20-
export MY_RESOURCE_GROUP_NAME="myResourceGroup$RANDOM_SUFFIX"
21-
export SCALE_SET_NAME="myScaleSet$RANDOM_SUFFIX"
22-
export NEW_INSTANCE_NAME="myNewInstance$RANDOM_SUFFIX"
23-
export REGION="WestUS2"
24-
```
25-
2618
## Setup Resource Group
2719
Before proceeding, ensure the resource group exists. This step creates the resource group if it does not already exist.
2820

2921
```bash
22+
export RANDOM_SUFFIX=$(openssl rand -hex 3)
23+
export MY_RESOURCE_GROUP_NAME="myResourceGroup$RANDOM_SUFFIX"
24+
export REGION="WestUS2"
3025
az group create --name $MY_RESOURCE_GROUP_NAME --location $REGION
3126
```
3227

@@ -49,6 +44,7 @@ az group create --name $MY_RESOURCE_GROUP_NAME --location $REGION
4944
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.
5045

5146
```azurecli-interactive
47+
export SCALE_SET_NAME="myScaleSet$RANDOM_SUFFIX"
5248
az vmss create \
5349
--resource-group $MY_RESOURCE_GROUP_NAME \
5450
--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
319315
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.
320316

321317
```azurecli-interactive
318+
export NEW_INSTANCE_NAME="myNewInstance$RANDOM_SUFFIX"
322319
az vm create --name $NEW_INSTANCE_NAME --resource-group $MY_RESOURCE_GROUP_NAME --vmss $SCALE_SET_NAME --image RHELRaw8LVMGen2
323320
```
324321

scenarios/azure-management-docs/articles/azure-linux/tutorial-azure-linux-add-nodepool.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -64,8 +64,6 @@ az aks nodepool add \
6464
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.
6565

6666
```azurecli-interactive
67-
export CLUSTER_NAME="myAKSClusterabcf37"
68-
export RESOURCE_GROUP="myAKSResourceGroupabcf37"
6967
az aks nodepool list --resource-group $RESOURCE_GROUP --cluster-name $CLUSTER_NAME
7068
```
7169

scenarios/azure-management-docs/articles/azure-linux/tutorial-azure-linux-create-cluster.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -38,8 +38,6 @@ When creating a resource group, it is required to specify a location. This locat
3838
Before running the command, environment variables are declared to ensure unique resource names for each deployment.
3939

4040
```bash
41-
export RANDOM_SUFFIX=c97736
42-
export RESOURCE_GROUP_NAME="testAzureLinuxResourceGroup${RANDOM_SUFFIX}"
4341
export REGION="EastUS2"
4442
az group create --name $RESOURCE_GROUP_NAME --location $REGION
4543
```
@@ -64,10 +62,9 @@ az group create --name $RESOURCE_GROUP_NAME --location $REGION
6462
6563
## Create an Azure Linux Container Host cluster
6664

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.
6866

6967
```bash
70-
export CLUSTER_NAME="testAzureLinuxCluster${RANDOM_SUFFIX}"
7168
az aks create --name $CLUSTER_NAME --resource-group $RESOURCE_GROUP_NAME --os-sku AzureLinux
7269
```
7370

scenarios/azure-management-docs/articles/azure-linux/tutorial-azure-linux-telemetry-monitor.md

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -26,15 +26,6 @@ In the next and last tutorial, you'll learn how to upgrade your Azure Linux node
2626
- 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).
2727
- 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).
2828

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.
32-
33-
```bash
34-
export RESOURCE_GROUP="myAKSResourceGroupabcf37"
35-
export CLUSTER_NAME="myAKSClusterabcf37"
36-
```
37-
3829
## Enable monitoring
3930

4031
## Connect to your cluster

0 commit comments

Comments
 (0)