Skip to content

Commit f13ef01

Browse files
committed
fix warnings
1 parent 20c0e77 commit f13ef01

File tree

3 files changed

+7
-7
lines changed

3 files changed

+7
-7
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -188,10 +188,10 @@ az aks update -n <cluster-name> -g <resource-group> --disable-azure-container-st
188188
> [!NOTE]
189189
> If you have an existing storage pool of the type that you're trying to disable, the storage pool type won't be disabled.
190190
191-
## Next steps
191+
## Next step
192192

193193
To create persistent volumes, select the link for the backing storage type you selected.
194194

195-
- [Create persistent volume claim with Azure managed disks](use-container-storage-with-managed-disks.md#create-a-persistent-volume-claim)
195+
- [Create persistent volume claim with Azure managed disks](use-container-storage-with-managed-disks.md#3-create-a-persistent-volume-claim)
196196
- [Create persistent volume claim with Ephemeral Disk](use-container-storage-with-local-disk.md#create-a-persistent-volume-claim)
197197
- [Create persistent volume claim with Azure Elastic SAN](use-container-storage-with-elastic-san.md#create-a-persistent-volume-claim)

articles/storage/container-storage/container-storage-introduction.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ Feature support depends on which backing storage option you select. The followin
7373
Based on feedback from customers, we've included the following capabilities with the latest preview update:
7474

7575
- Improve stateful application availability by using [multi-zone storage pools and ZRS disks](enable-multi-zone-redundancy.md).
76-
- Enable server-side encryption with [customer-managed keys](use-container-storage-with-managed-disks.md#enable-server-side-encryption-with-customer-managed-keys) (Azure Disks only).
76+
- Enable server-side encryption with [customer-managed keys](use-container-storage-with-managed-disks.md#create-a-dynamic-storage-pool-using-your-own-encryption-key-optional) (Azure Disks only).
7777
- Scale up by dynamically expanding [volumes](resize-volume.md) and storage pools backed by Azure Disks and Ephemeral Disk without downtime.
7878
- [Clone persistent volumes](clone-volume.md) within a storage pool.
7979
- Optimize applications with Azure Linux Container Host.

articles/storage/container-storage/use-container-storage-with-managed-disks.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ You have the following options for creating a storage pool:
3434
- [Create a pre-provisioned storage pool](#create-a-pre-provisioned-storage-pool) using pre-provisioned Azure managed disks
3535
- [Create a dynamic storage pool using your own encryption key (optional)](#create-a-dynamic-storage-pool-using-your-own-encryption-key-optional)
3636

37-
If you enabled Azure Container Storage using `az aks create` or `az aks update` commands, you might already have a storage pool. Use `kubectl get sp -n acstor` to get the list of storage pools. If you have a storage pool already available that you want to use, you can skip this step and proceed to [Display the available storage classes](#display-the-available-storage-classes).
37+
If you enabled Azure Container Storage using `az aks create` or `az aks update` commands, you might already have a storage pool. Use `kubectl get sp -n acstor` to get the list of storage pools. If you have a storage pool already available that you want to use, you can skip this step and proceed to [Display the available storage classes](#2-display-the-available-storage-classes).
3838

3939
#### Create a dynamic storage pool
4040

@@ -77,7 +77,7 @@ Follow these steps to create a dynamic storage pool for Azure Disks.
7777
kubectl describe sp <storage-pool-name> -n acstor
7878
```
7979

80-
When the storage pool is created, Azure Container Storage will create a storage class on your behalf, using the naming convention `acstor-<storage-pool-name>`. Now you can [display the available storage classes](#display-the-available-storage-classes) and [create a persistent volume claim](#create-a-persistent-volume-claim).
80+
When the storage pool is created, Azure Container Storage will create a storage class on your behalf, using the naming convention `acstor-<storage-pool-name>`. Now you can [display the available storage classes](#2-display-the-available-storage-classes) and [create a persistent volume claim](#3-create-a-persistent-volume-claim).
8181

8282
#### Create a pre-provisioned storage pool
8383

@@ -125,7 +125,7 @@ Follow these steps to create a pre-provisioned storage pool for Azure Disks.
125125
kubectl describe sp <storage-pool-name> -n acstor
126126
```
127127

128-
When the storage pool is created, Azure Container Storage will create a storage class on your behalf, using the naming convention `acstor-<storage-pool-name>`. Now you can [display the available storage classes](#display-the-available-storage-classes) and [create a persistent volume claim](#create-a-persistent-volume-claim).
128+
When the storage pool is created, Azure Container Storage will create a storage class on your behalf, using the naming convention `acstor-<storage-pool-name>`. Now you can [display the available storage classes](#2-display-the-available-storage-classes) and [create a persistent volume claim](#3-create-a-persistent-volume-claim).
129129

130130
#### Create a dynamic storage pool using your own encryption key (optional)
131131

@@ -308,7 +308,7 @@ To detach a persistent volume, delete the pod that the persistent volume is atta
308308
kubectl delete pods <pod-name>
309309
```
310310

311-
To reattach a persistent volume, simply reference the persistent volume claim name in the YAML manifest file as described in [Deploy a pod and attach a persistent volume](#deploy-a-pod-and-attach-a-persistent-volume).
311+
To reattach a persistent volume, simply reference the persistent volume claim name in the YAML manifest file as described in [Deploy a pod and attach a persistent volume](#4-deploy-a-pod-and-attach-a-persistent-volume).
312312

313313
To check which persistent volume a persistent volume claim is bound to, run `kubectl get pvc <persistent-volume-claim-name>`.
314314

0 commit comments

Comments
 (0)