Skip to content

Commit daacb61

Browse files
committed
Common codeblock markers on ACStor
1 parent d38920e commit daacb61

21 files changed

Lines changed: 116 additions & 116 deletions

articles/storage/container-storage/clone-volume.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ Follow the instructions below to clone a persistent volume.
9090
9191
1. Apply the YAML manifest file to deploy the new pod.
9292
93-
```azurecli-interactive
93+
```azurecli
9494
kubectl apply -f acstor-pod.yaml
9595
```
9696

@@ -102,7 +102,7 @@ Follow the instructions below to clone a persistent volume.
102102

103103
1. Check that the pod is running and that the persistent volume claim is bound successfully to the pod:
104104

105-
```azurecli-interactive
105+
```azurecli
106106
kubectl describe pod fiopod2
107107
kubectl describe pvc azurediskpvc
108108
```

articles/storage/container-storage/container-storage-aks-quickstart-version-1.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Azure Container Storage is a cloud-based volume management, deployment, and orch
3535

3636
Set your Azure subscription context using the `az account set` command. You can view the subscription IDs for all the subscriptions you have access to by running the `az account list --output table` command. Remember to replace `<subscription-id>` with your subscription ID.
3737

38-
```azurecli
38+
```azurecli-interactive
3939
az account set --subscription <subscription-id>
4040
```
4141

@@ -48,13 +48,13 @@ To connect to the cluster, use the Kubernetes command-line client, `kubectl`. It
4848
* Downloads credentials and configures the Kubernetes CLI to use them.
4949
* Uses `~/.kube/config`, the default location for the Kubernetes configuration file. You can specify a different location for your Kubernetes configuration file using the *--file* argument.
5050

51-
```azurecli-interactive
51+
```azurecli
5252
az aks get-credentials --resource-group <resource-group> --name <cluster-name>
5353
```
5454
5555
2. Verify the connection to your cluster using the `kubectl get` command. This command returns a list of the cluster nodes.
5656
57-
```azurecli-interactive
57+
```azurecli
5858
kubectl get nodes
5959
```
6060
@@ -151,13 +151,13 @@ If you want to install Azure Container Storage on specific node pools, follow th
151151

152152
1. Run the following command to view the list of available node pools. Replace `<resource-group>` and `<cluster-name>` with your own values.
153153

154-
```azurecli-interactive
154+
```azurecli
155155
az aks nodepool list --resource-group <resource-group> --cluster-name <cluster-name>
156156
```
157157

158158
2. Run the following command to install Azure Container Storage on specific node pools. Replace `<cluster-name>` and `<resource-group>` with your own values. Replace `<storage-pool-type>` with `azureDisk`, `ephemeralDisk`, or `elasticSan`. If you select `ephemeralDisk`, you can also specify --storage-pool-option, and the values can be `NVMe` or `Temp`.
159159

160-
```azurecli-interactive
160+
```azurecli
161161
az aks update -n <cluster-name> -g <resource-group> --enable-azure-container-storage <storage-pool-type> --container-storage-version 1 --azure-container-storage-nodepools <comma separated values of nodepool names>
162162
```
163163

articles/storage/container-storage/container-storage-faq.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Azure Container Storage is a cloud-based volume management, deployment, and orch
3636
**Installer-only (choose storage later)**
3737
Use this option when you want Azure Container Storage installed but plan to decide the storage backend later.
3838

39-
```azurecli
39+
```azurecli-interactive
4040
az aks update -n <cluster-name> -g <resource-group> --enable-azure-container-storage
4141
```
4242

@@ -131,7 +131,7 @@ Azure Container Storage is a cloud-based volume management, deployment, and orch
131131
**If I already have Azure Container Storage preview installed on my AKS cluster, how can I update to the latest GA version?**
132132
If you have autoupgrade turned on, Azure Container Storage updates to the latest version automatically. If you don't have autoupgrade turned on, we recommend updating to the latest generally available (GA) version by running the following command. Remember to replace `<cluster-name>` and `<resource-group>` with your own values.
133133

134-
```azurecli-interactive
134+
```azurecli
135135
az k8s-extension update --cluster-type managedClusters --cluster-name <cluster-name> --resource-group <resource-group> --name azurecontainerstorage --version 1.1.0 --auto-upgrade false --release-train stable
136136
```
137137

articles/storage/container-storage/enable-monitoring-version-1.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Prometheus metrics are stored in an Azure Monitor workspace, where you can analy
2424

2525
This feature only supports Azure Monitor managed service for Prometheus. If you have your own Prometheus instance deployed, then you must disable Azure Container Storage's Prometheus instance by running the following Azure CLI command. Replace `<cluster_name>` and `<resource_group_name>` with your own values.
2626

27-
```azurecli
27+
```azurecli-interactive
2828
az k8s-extension update --cluster-type managedClusters --cluster-name <cluster_name> --resource-group <resource_group_name> --name azurecontainerstorage --config base.metrics.enablePrometheusStack=false
2929
```
3030

articles/storage/container-storage/install-container-storage-aks-version-1.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ Azure Container Storage is a cloud-based volume management, deployment, and orch
4747

4848
Set your Azure subscription context using the `az account set` command. You can view the subscription IDs for all the subscriptions you have access to by running the `az account list --output table` command. Remember to replace `<subscription-id>` with your subscription ID.
4949

50-
```azurecli
50+
```azurecli-interactive
5151
az account set --subscription <subscription-id>
5252
```
5353

articles/storage/container-storage/install-container-storage-aks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ By the end of this tutorial, you can:
4242
- For existing clusters, ensure node pools already use a supported VM SKU before enabling Azure Container Storage.
4343

4444
- If you use Elastic SAN for the first time in the subscription, run this one-time registration command:
45-
```azurecli
45+
```azurecli-interactive
4646
az provider register --namespace Microsoft.ElasticSan
4747
```
4848

articles/storage/container-storage/install-container-storage-azure-arc.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -41,14 +41,14 @@ az account set --subscription <subscription-id>
4141

4242
The `Microsoft.ContainerService` and `Microsoft.KubernetesConfiguration` resource providers must be registered on your Azure subscription. To register these providers, run the following command:
4343

44-
```azurecli-interactive
44+
```azurecli
4545
az provider register --namespace Microsoft.ContainerService --wait
4646
az provider register --namespace Microsoft.KubernetesConfiguration --wait
4747
```
4848

4949
To check if these providers are registered successfully, run the following command:
5050

51-
```azurecli-interactive
51+
```azurecli
5252
az provider list --query "[?namespace=='Microsoft.ContainerService'].registrationState"
5353
az provider list --query "[?namespace=='Microsoft.KubernetesConfiguration'].registrationState"
5454
```
@@ -62,7 +62,7 @@ An Azure resource group is a logical group that holds your Azure resources that
6262

6363
Create a resource group using the `az group create` command. Replace `<resource-group-name>` with the name of the resource group you want to create, and replace `<location>` with an Azure region such as *eastus*, *westus2*, *westus3*, or *westeurope*.
6464

65-
```azurecli-interactive
65+
```azurecli
6666
az group create --name <resource-group-name> --location <location>
6767
```
6868

@@ -111,7 +111,7 @@ Run the following command to create a Linux-based AKS cluster and enable a syste
111111
Replace `<resource-group>` with the name of the resource group you created, `<cluster-name>` with the name of the cluster you want to create, and `<vm-type>` with the VM type you selected in the previous step. In this example, we create a cluster with three nodes. Increase the `--node-count` if you want a larger cluster. **If you want to use local NVMe for your storage pool type, be sure to set the node count to 4 or greater.**
112112

113113

114-
```azurecli-interactive
114+
```azurecli
115115
az aks create -g <resource-group> -n <cluster-name> --node-count 3 -s <vm-type> --generate-ssh-keys
116116
```
117117

@@ -129,13 +129,13 @@ To connect to the cluster, use the Kubernetes command-line client, `kubectl`. It
129129
* Downloads credentials and configures the Kubernetes CLI to use them.
130130
* Uses `~/.kube/config`, the default location for the Kubernetes configuration file. You can specify a different location for your Kubernetes configuration file using the *--file* argument.
131131

132-
```azurecli-interactive
132+
```azurecli
133133
az aks get-credentials --resource-group <resource-group> --name <cluster-name>
134134
```
135135
136136
2. Verify the connection to your cluster using the `kubectl get` command. This command returns a list of the cluster nodes.
137137
138-
```azurecli-interactive
138+
```azurecli
139139
kubectl get nodes
140140
```
141141
@@ -159,7 +159,7 @@ Next, you must update your node pool label to associate the node pool with the c
159159
160160
Run the following command to update the node pool label. Remember to replace `<resource-group>` and `<cluster-name>` with your own values, and replace `<nodepool-name>` with the name of your node pool.
161161
162-
```azurecli-interactive
162+
```azurecli
163163
az aks nodepool update --resource-group <resource-group> --cluster-name <cluster-name> --name <nodepool-name> --labels acstor.azure.com/io-engine=acstor
164164
```
165165

@@ -187,7 +187,7 @@ You only need to perform this step if you plan to use Azure Elastic SAN as backi
187187

188188
Run the following commands to assign **Azure Container Storage Operator** role to AKS managed identity. Remember to replace `<resource-group>`, `<cluster-name>`, and `<azure-subscription-id>` with your own values. You can also narrow the scope to your resource group, for example `/subscriptions/<azure-subscription-id>/resourceGroups/<resource-group>`.
189189

190-
```azurecli-interactive
190+
```azurecli
191191
export AKS_MI_OBJECT_ID=$(az aks show --name <cluster-name> --resource-group <resource-group> --query "identityProfile.kubeletidentity.objectId" -o tsv)
192192
az role assignment create --assignee $AKS_MI_OBJECT_ID --role "Azure Container Storage Operator" --scope "/subscriptions/<azure-subscription-id>"
193193
```
@@ -199,13 +199,13 @@ The initial install uses Azure Arc CLI commands to download a new extension. Rep
199199

200200
During installation, you might be asked to install the `k8s-extension`. Select **Y**.
201201

202-
```azurecli-interactive
202+
```azurecli
203203
az k8s-extension create --cluster-type managedClusters --cluster-name <cluster-name> --resource-group <resource-group> --name <extension-name> --extension-type microsoft.azurecontainerstorage --scope cluster --release-train stable --release-namespace acstor
204204
```
205205

206206
Installation takes 10-15 minutes to complete. You can check if the installation completed correctly by running the following command and ensuring that `provisioningState` says **Succeeded**:
207207

208-
```azurecli-interactive
208+
```azurecli
209209
az k8s-extension list --cluster-name <cluster-name> --resource-group <resource-group> --cluster-type managedClusters
210210
```
211211

articles/storage/container-storage/remove-container-storage-version-1.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,15 +28,15 @@ az aks update -n <cluster-name> -g <resource-group> --disable-azure-container-st
2828

2929
To delete an AKS cluster and all persistent volumes, run the following Azure CLI command. Replace `<resource-group>` and `<cluster-name>` with your own values.
3030

31-
```azurecli-interactive
31+
```azurecli
3232
az aks delete --resource-group <resource-group> --name <cluster-name>
3333
```
3434

3535
## Delete resource group
3636

3737
You can also use the [`az group delete`](/cli/azure/group) command to delete the resource group and all resources it contains. Replace `<resource-group>` with your resource group name.
3838

39-
```azurecli-interactive
39+
```azurecli
4040
az group delete --name <resource-group>
4141
```
4242

articles/storage/container-storage/remove-container-storage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Delete all persistent volume claims (PVCs) and persistent volumes (PVs) before u
2222

2323
Remove Azure Container Storage entirely by running the following Azure CLI command. Replace `<cluster-name>` and `<resource-group>` with your own values.
2424

25-
```azurecli
25+
```azurecli-interactive
2626
az aks update -n <cluster-name> -g <resource-group> --disable-azure-container-storage
2727
```
2828

articles/storage/container-storage/resize-volume-version-1.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ Follow these instructions to resize a persistent volume. A built-in storage clas
3838

3939
1. Check the PVC to make sure the volume is expanded:
4040

41-
```azurecli-interactive
41+
```azurecli
4242
kubectl describe pvc <pvc-name>
4343
```
4444

0 commit comments

Comments
 (0)