Merge pull request #278678 from khdownie/kendownie061924

update disks flow

Author: denrea

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

@@ -188,10 +188,10 @@ az aks update -n <cluster-name> -g <resource-group> --disable-azure-container-st
 > [!NOTE]
 > If you have an existing storage pool of the type that you're trying to disable, the storage pool type won't be disabled.
 
-## Next steps
+## Next step
 
 To create persistent volumes, select the link for the backing storage type you selected.
 
-- [Create persistent volume claim with Azure managed disks](use-container-storage-with-managed-disks.md#create-a-persistent-volume-claim)
+- [Create persistent volume claim with Azure managed disks](use-container-storage-with-managed-disks.md#3-create-a-persistent-volume-claim)
 - [Create persistent volume claim with Ephemeral Disk](use-container-storage-with-local-disk.md#create-a-persistent-volume-claim)
-- [Create persistent volume claim with Azure Elastic SAN](use-container-storage-with-elastic-san.md#create-a-persistent-volume-claim)
+- [Create persistent volume claim with Azure Elastic SAN](use-container-storage-with-elastic-san.md#3-create-a-persistent-volume-claim)

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

@@ -73,7 +73,7 @@ Feature support depends on which backing storage option you select. The followin
 Based on feedback from customers, we've included the following capabilities with the latest preview update:
 
 - Improve stateful application availability by using [multi-zone storage pools and ZRS disks](enable-multi-zone-redundancy.md).
-- 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).
+- 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).
 - Scale up by dynamically expanding [volumes](resize-volume.md) and storage pools backed by Azure Disks and Ephemeral Disk without downtime.
 - [Clone persistent volumes](clone-volume.md) within a storage pool.
 - Optimize applications with Azure Linux Container Host.

articles/storage/container-storage/use-container-storage-with-elastic-san.md

@@ -4,7 +4,7 @@ description: Configure Azure Container Storage for use with Azure Elastic SAN. C
 author: khdownie
 ms.service: azure-container-storage
 ms.topic: how-to
-ms.date: 05/30/2024
+ms.date: 06/19/2024
 ms.author: kendownie
 ms.custom: references_regions
 ---
@@ -17,7 +17,7 @@ ms.custom: references_regions
 
 [!INCLUDE [container-storage-prerequisites](../../../includes/container-storage-prerequisites.md)]
 
-- Ensure you have either an [Azure Container Storage Owner](../../role-based-access-control/built-in-roles/containers.md#azure-container-storage-owner) role or [Azure Container Storage Contributor](../../role-based-access-control/built-in-roles/containers.md#azure-container-storage-contributor) role on your subscription. Either of these roles will grant permissions that allow Azure Container Storage to communicate with the Elastic SAN resource. To make this change, go to your subscription page on the Azure Portal. Select **Access control (IAM) > Add role assignment** and search for either "Azure Container Storage Owner" or "Azure Container Storage Contributor" in the **Job function roles** tab. Select **View > Assignments > Add assignment** and add your account.
+- Ensure you have either an [Azure Container Storage Owner](../../role-based-access-control/built-in-roles/containers.md#azure-container-storage-owner) role or [Azure Container Storage Contributor](../../role-based-access-control/built-in-roles/containers.md#azure-container-storage-contributor) role on your subscription. Either of these roles will grant permissions that allow Azure Container Storage to communicate with the Elastic SAN resource. To make this change, go to your subscription page on the Azure portal. Select **Access control (IAM) > Add role assignment** and search for either "Azure Container Storage Owner" or "Azure Container Storage Contributor" in the **Job function roles** tab. Select **View > Assignments > Add assignment** and add your account.
 
 > [!NOTE]
 > To use Azure Container Storage with Azure Elastic SAN, your AKS cluster should have a node pool of at least three [general purpose VMs](../../virtual-machines/sizes-general.md) such as **standard_d4s_v5** for the cluster nodes, each with a minimum of four virtual CPUs (vCPUs).
@@ -33,11 +33,15 @@ The following features aren't currently supported when you use Azure Container S
 
 [!INCLUDE [container-storage-regions](../../../includes/container-storage-regions.md)]
 
-## Create a storage pool
+## Create and attach persistent volumes
+
+Follow these steps to create and attach a persistent volume.
+
+### 1. Create a storage pool
 
 First, create a storage pool, which is a logical grouping of storage for your Kubernetes cluster, by defining it in a YAML manifest file.
 
-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 section and proceed to [Display the available storage classes](#display-the-available-storage-classes).
+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 section and proceed to [Display the available storage classes](#2-display-the-available-storage-classes).
 
 Follow these steps to create a storage pool with Azure Elastic SAN.
 
@@ -78,7 +82,7 @@ Follow these steps to create a storage pool with Azure Elastic SAN.
 
 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>`. It will also create an Azure Elastic SAN resource.
 
-## Display the available storage classes
+### 2. Display the available storage classes
 
 When the storage pool is ready to use, you must select a storage class to define how storage is dynamically created when creating persistent volume claims and deploying persistent volumes.
 
@@ -87,9 +91,9 @@ Run `kubectl get sc` to display the available storage classes. You should see a
 > [!IMPORTANT]
 > Don't use the storage class that's marked **internal**. It's an internal storage class that's needed for Azure Container Storage to work.
 
-## Create a persistent volume claim
+### 3. Create a persistent volume claim
 
-A persistent volume claim (PVC) is used to automatically provision storage based on a storage class. Follow these steps to create a PVC using the new storage class. 
+A persistent volume claim (PVC) is used to automatically provision storage based on a storage class. Follow these steps to create a PVC using the new storage class.
 
 1. Use your favorite text editor to create a YAML manifest file such as `code acstor-pvc.yaml`.
 
@@ -129,7 +133,7 @@ A persistent volume claim (PVC) is used to automatically provision storage based
 
 Once the PVC is created, it's ready for use by a pod.
 
-## Deploy a pod and attach a persistent volume
+### 4. Deploy a pod and attach a persistent volume
 
 Create a pod using [Fio](https://github.com/axboe/fio) (Flexible I/O Tester) for benchmarking and workload simulation, and specify a mount path for the persistent volume. For **claimName**, use the **name** value that you used when creating the persistent volume claim.
 
@@ -187,19 +191,23 @@ Create a pod using [Fio](https://github.com/axboe/fio) (Flexible I/O Tester) for
 
 You've now deployed a pod that's using an Elastic SAN as its storage, and you can use it for your Kubernetes workloads.
 
-## Detach and reattach a persistent volume
+## Manage persistent volumes and storage pools
+
+Now that you've created a persistent volume, you can detach and reattach it as needed. You can also delete a storage pool.
+
+### Detach and reattach a persistent volume
 
 To detach a persistent volume, delete the pod that the persistent volume is attached to. Replace `<pod-name>` with the name of the pod, for example **fiopod**.
 
 ```azurecli-interactive
 kubectl delete pods <pod-name>
 ```
 
-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).
+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).
 
 To check which persistent volume a persistent volume claim is bound to, run `kubectl get pvc <persistent-volume-claim-name>`.
 
-## Delete a storage pool
+### Delete a storage pool
 
 If you want to delete a storage pool, run the following command. Replace `<storage-pool-name>` with the storage pool name.