Merge pull request #311443 from eh8/main

Clarify ACStor disclaimers and add ESAN intro

Author: prmerger-automator[bot]

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

@@ -18,7 +18,7 @@ Azure Container Storage is a cloud-based volume management, deployment, and orch
 
 * <a id="azure-container-storage-versions"></a>
   **What's the difference between Azure Container Storage version 2.x.x and version 1.x.x?**
-  Azure Container Storage (version 2.x.x) features a lighter weight, on-demand installation, and optimized resource utilization. However, version 2.x.x currently only supports Ephemeral Disk (Local NVMe) as backing storage, whereas version 1.x.x supports Azure Disks, Ephemeral Disk, and Azure Elastic SAN.
+  Azure Container Storage (version 2.x.x) features a lighter weight, on-demand installation, and optimized resource utilization. However, version 2.x.x currently supports local NVMe and Azure Elastic SAN as backing storage, whereas version 1.x.x supports Azure Disks, Ephemeral Disk (local NVMe and temp SSD), and Azure Elastic SAN.
 
 * <a id="azure-container-storage-applicability"></a>
   **What changes between Azure Container Storage versions 2.0.x and 2.1.x+?**

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

@@ -384,5 +384,6 @@ kubectl describe ocirepositories.source.installer.acstor.io -n kube-system
 ## Next steps
 
 - [Use Azure Container Storage with local NVMe](use-container-storage-with-local-disk.md)
+- [Use Azure Container Storage with Elastic SAN](use-container-storage-with-elastic-san.md)
 - [Overview of deploying a highly available PostgreSQL database on Azure Kubernetes Service (AKS)](/azure/aks/postgresql-ha-overview#storage-considerations)
 - [Frequently asked questions (FAQ) about Azure Container Storage](container-storage-faq.md)

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

@@ -14,9 +14,14 @@ ms.custom:
 
 # Use Azure Container Storage with Azure Elastic SAN
 
-Azure Container Storage is a cloud-based volume management, deployment, and orchestration service built for containers. Azure Elastic SAN is a fully integrated solution that simplifies deploying, scaling, and managing a storage area network (SAN), with built-in cloud capabilities such as high availability.
+[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 Azure Elastic SAN as back-end storage for your Kubernetes workloads. 
 
-This article shows how to configure Azure Container Storage to use Azure Elastic SAN. At the end, you can use Elastic SAN as a storage option for your stateful workloads.
+> [!IMPORTANT]
+> This article applies to [Azure Container Storage (version 2.x.x)](container-storage-introduction.md), which supports local NVMe disk and Azure Elastic SAN as backing storage types. For details about earlier versions, see [Azure Container Storage (version 1.x.x) documentation](container-storage-introduction-version-1.md).
+
+## What is Azure Elastic SAN?
+
+Azure Elastic SAN is a managed, shared block-storage service that provides a central pool of capacity and performance (IOPS and throughput) from which multiple volumes are created and attached to many compute resources. Instead of provisioning and tuning individual disks per workload, Elastic SAN lets you allocate storage from a single capacity pool and consume performance elastically across all attached volumes. This model is well suited to environments with many dynamic workloads—such as container platforms like Azure Kubernetes Service—where demand varies over time and unused performance on one volume can be used by another. Elastic SAN is typically used when you need shared, scalable block storage across many volumes or nodes, faster volume attach/detach for orchestrated workloads, support for higher volume density per node, and a single place to provision and manage storage capacity and performance.
 
 ## Prerequisites
 
@@ -36,11 +41,11 @@ Azure Container Storage supports three ways to use Elastic SAN with Azure Kubern
 - **Pre-provisioned Elastic SAN and volume group**: You create the Elastic SAN and volume group first, then Azure Container Storage provisions volumes within those existing resources.
 - **Static provisioning**: You pre-create the Elastic SAN, volume group, and volume, then surface the volume to Kubernetes as a statically defined persistent volume (PV).
 
-The following sections show how to configure a StorageClass for each model.
+The following sections show how to configure a storage class for each model.
 
 ## Dynamic provisioning of Elastic SAN
 
-### Create a default StorageClass
+### Create a default storage class
 
 Create a YAML manifest file such as `storageclass.yaml`, then use the following specification.
 
@@ -55,11 +60,11 @@ volumeBindingMode: Immediate
 allowVolumeExpansion: true
 ```
 
-The default Elastic SAN capacity provisioned with this StorageClass is 1 TiB.
+The default Elastic SAN capacity provisioned with this storage class is 1 TiB.
 
-### Create a StorageClass with custom Elastic SAN capacity
+### Create a storage class with custom Elastic SAN capacity
 
-If you need a different initial capacity than the default 1 TiB, set the `initialStorageTiB` parameter in the StorageClass.
+If you need a different initial capacity than the default 1 TiB, set the `initialStorageTiB` parameter in the storage class.
 
 ```yaml
 apiVersion: storage.k8s.io/v1
@@ -76,9 +81,11 @@ parameters:
 
 ## Pre-provisioned Elastic SAN and volume groups
 
-You can pre-create an Elastic SAN or an Elastic SAN and volume group, then reference those resources in the StorageClass.
+You can pre-create an Elastic SAN or an Elastic SAN and volume group, then reference those resources in the storage class.
+
+### Create a storage class for a pre-provisioned Elastic SAN
 
-### Create a StorageClass for a pre-provisioned Elastic SAN
+If you haven't already done so, [install Azure Container Storage.](install-container-storage-aks.md) 
 
 1. Identify the managed resource group of the AKS cluster.
 
@@ -94,7 +101,7 @@ You can pre-create an Elastic SAN or an Elastic SAN and volume group, then refer
    az elastic-san create --resource-group <node-resource-group> --name <san-name> --location <node-region> --sku Premium_ZRS --base-size-tib 1 --extended-capacity-size-tib 1
    ```
 
-1. Create a StorageClass that references the Elastic SAN:
+1. Create a storage class that references the Elastic SAN:
 
    ```yaml
    apiVersion: storage.k8s.io/v1
@@ -109,7 +116,7 @@ You can pre-create an Elastic SAN or an Elastic SAN and volume group, then refer
      san: <san-name> # replace with the name of your pre-created Elastic SAN
    ```
 
-### Create a StorageClass for a pre-provisioned Elastic SAN and volume group
+### Create a storage class for a pre-provisioned Elastic SAN and volume group
 
 1. Repeat the steps above to create an Elastic SAN in the managed resource group.
 
@@ -139,7 +146,7 @@ You can pre-create an Elastic SAN or an Elastic SAN and volume group, then refer
    az elastic-san volume-group create --resource-group <node-resource-group> --elastic-san-name <san-name> --name <volume-group-name> --network-acls '{"virtual-network-rules":[{"id":"<subnet-id>","action":"Allow"}]}'
    ```
 
-1. Create a StorageClass that references the Elastic SAN and volume group:
+1. Create a storage class that references the Elastic SAN and volume group:
 
    ```yaml
    apiVersion: storage.k8s.io/v1
@@ -155,15 +162,15 @@ You can pre-create an Elastic SAN or an Elastic SAN and volume group, then refer
      volumegroup: <volume-group-name> # replace with the name of your pre-created volume group
    ```
 
-## Apply the manifest and verify StorageClass creation
+## Apply the manifest and verify storage class creation
 
 Apply the manifest:
 
 ```azurecli
 kubectl apply -f storageclass.yaml
 ```
 
-Verify that the StorageClass is created:
+Verify that the storage class is created:
 
 ```azurecli
 kubectl get storageclass azuresan
@@ -178,7 +185,7 @@ azuresan   san.csi.azure.com    Delete          Immediate           true
 
 ## Create a persistent volume claim
 
-A persistent volume claim (PVC) automatically provisions storage based on a StorageClass. Follow these steps to create a PVC using the new StorageClass.
+A persistent volume claim (PVC) automatically provisions storage based on a storage class. Follow these steps to create a PVC using the new storage class.
 
 1. Create a YAML manifest file such as `acstor-pvc.yaml`.
 
@@ -274,9 +281,9 @@ You now have a pod that uses Elastic SAN for storage.
 
 You can pre-create the volume in Elastic SAN and surface it to Kubernetes as a static PV. Use the steps above to create the Elastic SAN and volume group. You can also perform these steps in the Azure portal by using the [Elastic SAN service blade](../elastic-san/elastic-san-create.md).
 
-### Create a default Elastic SAN StorageClass
+### Create a default Elastic SAN storage class
 
-Use the following YAML manifest to create a default Elastic SAN StorageClass:
+Use the following YAML manifest to create a default Elastic SAN storage class:
 
 ```yaml
 apiVersion: storage.k8s.io/v1
@@ -289,13 +296,13 @@ volumeBindingMode: Immediate
 allowVolumeExpansion: true
 ```
 
-Apply the manifest to create the StorageClass:
+Apply the manifest to create the storage class:
 
 ```azurecli
 kubectl apply -f storageclass.yaml
 ```
 
-Verify the StorageClass:
+Verify the storage class:
 
 ```azurecli
 kubectl get storageclass azuresan

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

@@ -15,7 +15,7 @@ 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 local NVMe disk as back-end storage for your Kubernetes workloads. NVMe is designed for high-speed data transfer between storage and CPU, providing high IOPS and throughput.
 
 > [!IMPORTANT]
-> This article applies to [Azure Container Storage (version 2.x.x)](container-storage-introduction.md), which currently only supports local NVMe disk for backing storage. For details about earlier versions, see [Azure Container Storage (version 1.x.x) documentation](container-storage-introduction-version-1.md).
+> This article applies to [Azure Container Storage (version 2.x.x)](container-storage-introduction.md), which supports local NVMe disk and Azure Elastic SAN as backing storage types. For details about earlier versions, see [Azure Container Storage (version 1.x.x) documentation](container-storage-introduction-version-1.md).
 
 ## What is local NVMe?
 

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

@@ -15,7 +15,7 @@ ms.custom: references_regions
 Azure Container Storage is a cloud-based volume management, deployment, and orchestration service built natively for containers. This article shows you how to configure Azure Container Storage (version 1.x.x) to use Azure managed disks as back-end storage for your Kubernetes workloads. At the end, you have a pod that's using Azure managed disks as its storage.
 
 > [!IMPORTANT]
-> This article covers features and capabilities available in Azure Container Storage (version 1.x.x). [Azure Container Storage (version 2.x.x)](container-storage-introduction.md) is now available, but it currently only supports local NVMe for backing storage.
+> This article covers features and capabilities available in Azure Container Storage (version 1.x.x). [Azure Container Storage (version 2.x.x)](container-storage-introduction.md) is now available and supports local NVMe and Azure Elastic SAN for backing storage.
 
 ## Prerequisites
 

articles/storage/container-storage/use-container-storage-with-temp-ssd.md

@@ -15,7 +15,7 @@ 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 (version 1.x.x) to use Ephemeral Disk with temp SSD as back-end storage for your Kubernetes workloads. At the end, you'll have a pod that's using temp SSD as its storage.
 
 > [!IMPORTANT]
-> This article covers features and capabilities available in Azure Container Storage (version 1.x.x). [Azure Container Storage (version 2.x.x)](container-storage-introduction.md) is now available, but it currently only supports local NVMe for backing storage.
+> This article covers features and capabilities available in Azure Container Storage (version 1.x.x). [Azure Container Storage (version 2.x.x)](container-storage-introduction.md) is now available and supports local NVMe and Azure Elastic SAN for backing storage.
 
 ## What is Ephemeral Disk?