Merge pull request #276270 from fhryo-msft/patch-24

Update use-container-storage-with-local-disk.md

Author: prmerger-automator[bot]

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

@@ -77,7 +77,7 @@ Based on feedback from customers, we've included the following capabilities with
 - 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.
-- Increase resiliency for applications using [local NVMe volumes with replication](use-container-storage-with-local-disk.md#optional-create-storage-pool-with-volume-replication-nvme-only).
+- Increase resiliency for applications using [local NVMe volumes with replication](use-container-storage-with-local-disk.md#create-storage-pool-with-volume-replication-nvme-only).
 
 For more information on these features, email the Azure Container Storage team at [email protected].
 

articles/storage/container-storage/troubleshoot-container-storage.md

@@ -69,7 +69,7 @@ To resolve this, sign in to the [Azure portal](https://portal.azure.com?azure-po
 ### Can't create persistent volumes from ephemeral disk storage pools
 Because ephemeral disks (local NVMe and Temp SSD) are ephemeral and not durable, we enforce the use of [Kubernetes Generic Ephemeral Volumes](https://kubernetes.io/docs/concepts/storage/ephemeral-volumes/#generic-ephemeral-volumes). If you try to create a persistent volume claim using an ephemeral disk pool, you'll see the following error: *Error from server (Forbidden): error when creating "eph-pvc.yaml": admission webhook "pvc.acstor.azure.com" denied the request: only generic ephemeral volumes are allowed in unreplicated ephemeralDisk storage pools*.
 
-If you need a persistent volume, where the volume has a lifecycle independent of any individual pod that's using the volume, Azure Container Storage supports replication for NVMe. You can create a storage pool with replication and create persistent volumes from there. See [Create storage pool with volume replication](use-container-storage-with-local-disk.md#optional-create-storage-pool-with-volume-replication-nvme-only) for guidance. Note that because ephemeral disk storage pools consume all the available NVMe disks, you must delete any existing ephemeral disk storage pools before creating a new storage pool with replication enabled. If you don't need persistence, you can create a generic ephemeral volume.
+If you need a persistent volume, where the volume has a lifecycle independent of any individual pod that's using the volume, Azure Container Storage supports replication for NVMe. You can create a storage pool with replication and create persistent volumes from there. See [Create storage pool with volume replication](use-container-storage-with-local-disk.md#create-storage-pool-with-volume-replication-nvme-only) for guidance. Note that because ephemeral disk storage pools consume all the available NVMe disks, you must delete any existing ephemeral disk storage pools before creating a new storage pool with replication enabled. If you don't need persistence, you can create a generic ephemeral volume.
 
 ## See also
 

articles/storage/container-storage/use-container-storage-with-local-disk.md

@@ -14,20 +14,25 @@ ms.custom: references_regions
 [Azure Container Storage](container-storage-introduction.md) is a cloud-based volume management, deployment, and orchestration service built natively for containers. This article shows you how to configure Azure Container Storage to use Ephemeral Disk as back-end storage for your Kubernetes workloads. At the end, you'll have a pod that's using either local NVMe or temp SSD as its storage.
 
 > [!IMPORTANT]
-> Local disks are ephemeral, meaning that they're created on the local virtual machine (VM) storage and not saved to an Azure storage service. Data will be lost on these disks if you stop/deallocate your VM. You can only create [Kubernetes generic ephemeral volumes](https://kubernetes.io/docs/concepts/storage/ephemeral-volumes/#generic-ephemeral-volumes) from an Ephemeral Disk storage pool. If you want to create a persistent volume, you have to enable [replication for your storage pool](#optional-create-storage-pool-with-volume-replication-nvme-only).
+> Local disks are ephemeral, meaning that they're created on the local virtual machine (VM) storage and not saved to an Azure storage service. Data will be lost on these disks if you stop/deallocate your VM. You can only create [Kubernetes generic ephemeral volumes](https://kubernetes.io/docs/concepts/storage/ephemeral-volumes/#generic-ephemeral-volumes) from an Ephemeral Disk storage pool. If you want to create a persistent volume, you have to enable [replication for your storage pool](#create-storage-pool-with-volume-replication-nvme-only).
 
 ## Prerequisites
 
 [!INCLUDE [container-storage-prerequisites](../../../includes/container-storage-prerequisites.md)]
 
 - If you haven't already installed Azure Container Storage, follow the instructions in [Install Azure Container Storage](container-storage-aks-quickstart.md).
+- Check if your target region is supported in [Azure Container Storage regions](container-storage-introduction.md#regional-availability)
 
-> [!NOTE]
-> To use Azure Container Storage with Ephemeral Disk, your AKS cluster should have a node pool of at least three [storage optimized VMs](../../virtual-machines/sizes-storage.md) such as **standard_l8s_v3**. We recommend that each VM have a minimum of four virtual CPUs (vCPUs).
+## Ensure VM with Ephemeral Disk support
 
-## Regional availability
+Ephemeral Disk is available in certain types of VM. If you plan to use Ephemeral Disk with local NVMe, a [storage optimized VM](../../virtual-machines/sizes-storage.md) such as **standard_l8s_v3** is required. If you plan to use Ephemeral Disk with temp SSD, a [Ev3 and Esv3-series VM](../../virtual-machines/ev3-esv3-series.md) is required.
 
-[!INCLUDE [container-storage-regions](../../../includes/container-storage-regions.md)]
+You can run the following command to get VM type that is used with your node pool.
+```azurecli-interactive
+az aks nodepool list --resource-group <resource group> --cluster-name <cluster name> --query "[].{PoolName:name, VmSize:vmSize}" -o table
+```
+
+We recommend that each VM have a minimum of four virtual CPUs (vCPUs), and each node pool have at least three nodes.
 
 ## Create a storage pool
 
@@ -39,7 +44,7 @@ You have three options to create a storage pool that uses Ephemeral Disk:
 
 - [Create storage pool with local NVMe](#create-a-storage-pool-with-nvme)
 - [Create storage pool with temp SSD](#create-a-storage-pool-with-temp-ssd)
-- [Create storage pool with local NVMe and replication](#optional-create-storage-pool-with-volume-replication-nvme-only)
+- [Create storage pool with local NVMe and replication](#create-storage-pool-with-volume-replication-nvme-only)
 
 ### Create a storage pool with NVMe
 
@@ -219,7 +224,7 @@ If you want to delete a storage pool, run the following command. Replace `<stora
 kubectl delete sp -n acstor <storage-pool-name>
 ```
 
-## Optional: Create storage pool with volume replication (NVMe only)
+## Create storage pool with volume replication (NVMe only)
 
 Applications that use local NVMe can leverage storage replication for improved resiliency. Replication isn't currently supported for temp SSD.
 
@@ -232,7 +237,6 @@ Follow these steps to create a storage pool using local NVMe with replication.
 
 1. Use your favorite text editor to create a YAML manifest file such as `code acstor-storagepool.yaml`.
 
-
 1. Paste in the following code and save the file. The storage pool **name** value can be whatever you want. Set replicas to 3 or 5.
 
    ```yml
@@ -370,15 +374,20 @@ You've now deployed a pod that's using Ephemeral Disk as its storage, and you ca
 
 ## 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**.
+To detach a persistent volume, delete the pod that the persistent volume is attached to.
 
 ```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 check which persistent volume a persistent volume claim is bound to, run `kubectl get pvc <persistent-volume-claim-name>`.
+To check which persistent volume a persistent volume claim is bound to, run:
+
+```azurecli-interactive
+kubectl get pvc <persistent-volume-claim-name>
+```
+
 
 ## See also