Merge pull request #311665 from eh8/main

Address Acrolinx feedback and clean up ESAN permissions setup

Author: Carolyn135

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

@@ -19,8 +19,10 @@ You can clone persistent volumes in Azure Container Storage (version 1.x.x). A c
 ## Prerequisites
 
 [!INCLUDE [container-storage-prerequisites](../../../includes/container-storage-prerequisites.md)]
-- You'll need an Azure Kubernetes Service (AKS) cluster with a node pool of at least three virtual machines (VMs) for the cluster nodes, each with a minimum of four virtual CPUs (vCPUs).
-- This article assumes you've already installed Azure Container Storage on your AKS cluster, and that you've created a storage pool and persistent volume claim (PVC) using either [Azure Disks](use-container-storage-with-managed-disks.md) or [ephemeral disk (local storage)](use-container-storage-with-local-disk-version-1.md). Azure Elastic SAN doesn't support resizing volumes.
+
+- You need an Azure Kubernetes Service (AKS) cluster with a node pool of at least three virtual machines (VMs) for the cluster nodes, each with a minimum of four virtual CPUs (vCPUs).
+
+- This article assumes your AKS cluster already runs Azure Container Storage and has a storage pool and persistent volume claim (PVC) created with either [Azure Disks](use-container-storage-with-managed-disks.md) or [ephemeral disk (local storage)](use-container-storage-with-local-disk-version-1.md). Azure Elastic SAN doesn't support resizing volumes.
 
 ## Clone a volume
 
@@ -88,19 +90,19 @@ Follow the instructions below to clone a persistent volume.
 
 1. Apply the YAML manifest file to deploy the new pod.
    
-   ```azurecli-interactive
+   ```azurecli
    kubectl apply -f acstor-pod.yaml
    ```
 
-   You should see output similar to the following:
+   You should see output similar to this example:
 
    ```output
    pod/fiopod2 created
    ```
 
-1. Check that the pod is running and that the persistent volume claim has been bound successfully to the pod:
+1. Check that the pod is running and that the persistent volume claim is bound successfully to the pod:
 
-   ```azurecli-interactive
+   ```azurecli
    kubectl describe pod fiopod2
    kubectl describe pvc azurediskpvc
    ```

articles/storage/container-storage/configure-encryption-for-elastic-san.md

@@ -18,6 +18,7 @@ This article shows how to configure encryption for an Elastic SAN volume group b
 ## Prerequisites
 
 [!INCLUDE [container-storage-prerequisites](../../../includes/container-storage-prerequisites.md)]
+
 - This article assumes you [installed Azure Container Storage version 2.1.0 or later](./install-container-storage-aks.md) on your Azure Kubernetes Service (AKS) cluster.
 
 ## Configure the key vault
@@ -165,7 +166,7 @@ Apply the manifest to deploy the pod.
 kubectl apply -f acstor-pod.yaml
 ```
 
-You should see output similar to the following:
+You should see output similar to this example:
 
 ```output
 pod/pod-san-encrypted created

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

@@ -21,12 +21,12 @@ Azure Container Storage is a cloud-based volume management, deployment, and orch
 Azure Container Storage pricing comprises two components:
 
 - The cost of the **backing storage resources** you choose: Azure Disks, Ephemeral Disk, or Azure Elastic SAN.
-- A **service fee** for Azure Container Storage orchestration. This fee only applies to storage pools larger than 5 TiB. If the storage pool is less than 5 TiB, there is no service fee. If the storage pool is greater than 5 TiB, the storage fee is based on the amount by which the storage pool capacity exceeds 5 TiB. For example, if you deploy a 9 TiB storage pool, the service fee will be calculated on 4 TiB.
+- A **service fee** for Azure Container Storage orchestration. This fee only applies to storage pools larger than 5 TiB. If the storage pool is less than 5 TiB, there is no service fee. If the storage pool is greater than 5 TiB, the storage fee is based on the amount by which the storage pool capacity exceeds 5 TiB. For example, if you deploy a 9 TiB storage pool, the service fee is calculated on 4 TiB.
 
 The amount of the Azure Container Storage service fee (if applicable) varies by target region. See [Azure Container Storage Pricing](https://aka.ms/AzureContainerStoragePricingPage) for details.
 
 > [!NOTE]
-> If your Azure Container Storage deployment isn't in the **Active** state, for example if you've stopped the Azure Kubernetes Service (AKS) cluster on which Azure Container Storage is installed, the service fee won't apply. However, you'll still be charged for the backing storage.
+> If your Azure Container Storage deployment isn't in the **Active** state, for example if you stop the Azure Kubernetes Service (AKS) cluster on which Azure Container Storage is installed, the service fee doesn't apply. However, you are still charged for the backing storage.
 
 ## Azure Container Storage with Azure Disks
 
@@ -50,7 +50,7 @@ See [Azure Managed Disks pricing](https://azure.microsoft.com/pricing/details/ma
 
 ## Azure Container Storage with Ephemeral Disk
 
-If you're using ephemeral disks on your AKS cluster nodes, you won't be charged for backing storage, as this is already included as part of your AKS virtual machine (VM) costs. If you deploy storage pools greater than 5 TiB in capacity, you'll be charged the Azure Container Storage service fee. Otherwise, the cost to use Azure Container Storage with Ephemeral Disk is zero.
+If you're using ephemeral disks on your AKS cluster nodes, you aren't charged for backing storage, as this is already included as part of your AKS virtual machine (VM) costs. If you deploy storage pools greater than 5 TiB in capacity, you are charged the Azure Container Storage service fee. Otherwise, the cost to use Azure Container Storage with Ephemeral Disk is zero.
 
 ## Azure Container Storage with Azure Elastic SAN
 

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

@@ -36,7 +36,7 @@ Azure Container Storage is a cloud-based volume management, deployment, and orch
   **Installer-only (choose storage later)**  
   Use this option when you want Azure Container Storage installed but plan to decide the storage backend later.
 
-  ```azurecli
+  ```azurecli-interactive
   az aks update -n <cluster-name> -g <resource-group> --enable-azure-container-storage
   ```
 
@@ -131,7 +131,7 @@ Azure Container Storage is a cloud-based volume management, deployment, and orch
   **If I already have Azure Container Storage preview installed on my AKS cluster, how can I update to the latest GA version?**  
   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.
 
-  ```azurecli-interactive
+  ```azurecli
   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
   ```
 

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

@@ -17,14 +17,14 @@ Azure Container Storage is a cloud-based volume management, deployment, and orch
 > [!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.
 > Azure Container Storage isn't available in all Azure regions. See [regional availability](#regional-availability).
-> If you previously installed the Azure Container Storage preview and don't have auto-upgrade enabled, be sure to [update to the GA version](container-storage-aks-quickstart-version-1.md#install-azure-container-storage-on-your-aks-cluster).
+> If you previously installed the Azure Container Storage preview and autoupgrade is off, [update to the GA version](container-storage-aks-quickstart-version-1.md#install-azure-container-storage-on-your-aks-cluster).
 
 :::row:::
     :::column:::
         > [!VIDEO https://learn-video.azurefd.net/vod/player?id=0e3cc19a-f57b-4b72-856e-481b42dfacd0]
     :::column-end:::
     :::column:::
-        This video provides an introduction to Azure Container Storage (version 1.x.x), an end-to-end storage management and orchestration service for stateful applications. Learn how to optimize the performance of stateful workloads on Azure Kubernetes Service (AKS) to effectively scale across storage services while providing a cost-effective, container-native experience.
+        This video provides an introduction to Azure Container Storage (version 1.x.x), an end-to-end storage management and orchestration service for stateful applications. Learn how to improve stateful workload speed on Azure Kubernetes Service (AKS). The video shows how to scale across storage services and keep a cost-efficient, container-native setup.
    :::column-end:::
 :::row-end:::
 
@@ -36,9 +36,9 @@ Azure Container Storage (version 1.x.x) offers persistent volume support with Re
 
 | **Storage type** | **Description** | **Workloads** | **Offerings** | **Provisioning model** |
 |------------------|-----------------|---------------|---------------|------------------------|
-| **[Azure Elastic SAN](../elastic-san/elastic-san-introduction.md)** (Preview)| Provision on demand, fully managed resource | General purpose databases, streaming and messaging services, CD/CI environments, and other tier 1/tier 2 workloads. | Azure Elastic SAN | Provisioned on demand per created volume and volume snapshot. Multiple clusters can access a single SAN concurrently, however persistent volumes can only be attached by one consumer at a time. |
+| **[Azure Elastic SAN](../elastic-san/elastic-san-introduction.md)** (Preview)| Provision on demand, fully managed resource | General purpose databases, streaming and messaging services, CD/CI environments, and other tier 1/tier 2 workloads. | Azure Elastic SAN | Provisioned on demand per created volume and volume snapshot. Multiple clusters can access a single SAN at the same time. Only one consumer can attach a persistent volume at a time. |
 | **[Azure Disks](/azure/virtual-machines/managed-disks-overview)** | Granular control of storage SKUs and configurations​ | Azure Disks are a good fit for tier 1 and general purpose databases such as MySQL, MongoDB, and PostgreSQL. | Premium SSD, Premium SSD v2, Standard SSD, Ultra Disk | Provisioned per target container storage pool size and maximum volume size. |
-| **Ephemeral Disk** | Utilizes local storage resources on AKS nodes (NVMe or temp SSD) | Ephemeral disk is extremely latency sensitive (low sub-ms latency), so it's best for applications with no data durability requirement or with built-in data replication support such as Cassandra. | NVMe is available on some Azure VM SKUs, for example, [Storage optimized VM SKUs](/azure/virtual-machines/sizes/overview#storage-optimized) or [GPU accelerated VM SKUs](/azure/virtual-machines/sizes/overview#gpu-accelerated) | Deployed as part of the VMs hosting an AKS cluster. AKS discovers the available ephemeral storage on AKS nodes and acquires them for volume deployment. |
+| **Ephemeral Disk** | Utilizes local storage resources on AKS nodes (NVMe or temp SSD) | Ephemeral disk has sub-ms latency, so it's best for applications that don't require data durability or that include data replication, such as Cassandra. | NVMe is available on some Azure VM SKUs, for example, [Storage optimized VM SKUs](/azure/virtual-machines/sizes/overview#storage-optimized) or [GPU accelerated VM SKUs](/azure/virtual-machines/sizes/overview#gpu-accelerated) | Deployed as part of the VMs hosting an AKS cluster. AKS discovers the available ephemeral storage on AKS nodes and acquires them for volume deployment. |
 
 ### Feature support for different storage types
 
@@ -63,7 +63,7 @@ Feature support depends on which backing storage option you select. The followin
 
 ## What's new in Azure Container Storage
 
-Our latest updates enhance the resiliency and performance of stateful containers. We now offer multi-zone storage pools and volume replication for local NVMe storage pools, ensuring availability during single node failures. Snapshot support is available across all storage options for backup and disaster recovery. Additionally, the Ephemeral Disk portfolio now includes temp SSD support, providing cost-efficient solutions for use cases leveraging directly attached local storage: 
+Our latest updates enhance the resiliency and performance of stateful containers. We now offer multi-zone storage pools and volume replication for local NVMe storage pools, ensuring availability during single node failures. Snapshot support is available across all storage options for backup and disaster recovery. Additionally, the Ephemeral Disk portfolio now includes temp SSD support. This support provides cost-efficient options for use cases that use directly attached local storage: 
 
 - Enhance the resiliency of your persistent volumes hosted on local NVMe storage with replication support.
 - Improved persistent volume recovery after a restart of an Azure Kubernetes Service (AKS) cluster.
@@ -79,7 +79,7 @@ With Azure Container Storage, you don't need to worry about configuring individu
 
 You can use Azure Container Storage to:
 
-- **Accelerate VM-to-container initiatives:** Azure Container Storage surfaces the full spectrum of Azure block storage offerings that were previously only available for VMs and makes them available for containers. This includes ephemeral disk that provides extremely low latency for workloads like Cassandra, as well as Azure Elastic SAN (Preview) that provides native iSCSI and shared provisioned targets.
+- **Accelerate VM-to-container initiatives:** Azure Container Storage surfaces the full spectrum of Azure block storage offerings that were previously only available for VMs and makes them available for containers. This includes ephemeral disk that provides low latency for workloads like Cassandra, and Azure Elastic SAN (Preview) that provides native iSCSI and shared provisioned targets.
 
 - **Simplify volume management with Kubernetes:** By providing volume orchestration via the Kubernetes control plane, Azure Container Storage makes it easy to deploy and manage volumes within Kubernetes - without the need to move back and forth between different control planes.
 
@@ -89,7 +89,7 @@ You can use Azure Container Storage to:
 
 - **Rapid scale out of stateful pods:** Azure Container Storage mounts persistent volumes over network block storage protocols (NVMe-oF or iSCSI), offering fast attach and detach of persistent volumes. You can start small and deploy resources as needed while making sure your applications aren't starved or disrupted, either during initialization or in production. Application resiliency is improved with pod respawns across the cluster, requiring rapid movement of persistent volumes. Leveraging remote network protocols, Azure Container Storage tightly couples with the pod lifecycle to support highly resilient, high-scale stateful applications on AKS.
 
-- **Improved performance for stateful workloads:** Azure Container Storage enables superior read performance and provides near-disk write performance by using NVMe-oF over TCP. This allows customers to cost-effectively meet performance requirements for various container workloads including tier 1 I/O intensive, general purpose, throughput sensitive, and dev/test. Accelerate the attach/detach time of persistent volumes and minimize pod failover time.
+- **Improved performance for stateful workloads:** Azure Container Storage enables superior read performance and provides near-disk write performance by using NVMe-oF over TCP. This capability helps customers meet performance requirements for container workloads including tier 1 I/O-intensive, general-purpose, throughput-sensitive, and dev/test workloads. Accelerate the attach/detach time of persistent volumes and minimize pod failover time.
 
 - **Kubernetes-native volume orchestration:** Create storage pools and persistent volumes, capture snapshots, and manage the entire lifecycle of volumes using `kubectl` commands without switching between toolsets for different control plane operations.
 

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

@@ -25,7 +25,7 @@ Azure Container Storage gives your container workloads access to high-performanc
 
 Local NVMe disks provide the highest performance storage in Azure. They are ideal for latency-sensitive workloads like PostgreSQL and compute-intensive AI and ML frameworks like Ray and Kubeflow.
 
-[Elastic SAN](../elastic-san/elastic-san-introduction.md) support in Azure Container Storage lets you use durable, network-attached block storage that scales with your application. By provisioning volumes from an Elastic SAN volume group, you gain predictable throughput and built-in redundancy options such as locally redundant storage (LRS) and zone-redundant storage (ZRS). This makes Azure Container Storage a strong choice for databases, analytics engines, and any workload that needs consistent performance.
+[Elastic SAN](../elastic-san/elastic-san-introduction.md) support in Azure Container Storage lets you use durable, network-attached block storage that scales with your application. By provisioning volumes from an Elastic SAN volume group, you gain predictable throughput and built-in redundancy options such as locally redundant storage (LRS) and zone-redundant storage (ZRS). This capability makes Azure Container Storage a strong choice for databases, analytics engines, and any workload that needs consistent performance.
 
 You can create and manage storage volumes using standard Kubernetes tools. You don't need to switch between portals or install Container Storage Interface (CSI) drivers yourself.
 
@@ -34,7 +34,7 @@ Azure Container Storage works with Azure Kubernetes Service (AKS) and self-manag
 ## Key benefits
 
 - **Seamless scaling of stateful pods:** Azure Container Storage mounts persistent volumes by using NVMe over Fabrics (NVMe-oF) or iSCSI (Internet Small Computer System Interface). This speeds attach and detach operations and supports fast pod recovery. When used with Elastic SAN, Azure Container Storage can provision and attach thousands of persistent volumes per cluster. This avoids bottlenecks such as Azure Resource Manager disk attachment limits (for example, 64 disks per VM).
-- **Optimized performance for stateful workloads:** Azure Container Storage delivers high read throughput and near-native disk write speeds by using NVMe-oF over TCP. This enables cost-effective performance for tier 1 I/O-intensive, general-purpose, throughput-sensitive, and development/test workloads.
+- **Optimized performance for stateful workloads:** Azure Container Storage delivers high read throughput and near-native disk write speeds by using NVMe-oF over TCP. This approach enables cost-effective performance for tier 1 I/O-intensive, general-purpose, throughput-sensitive, and development/test workloads.
 - **Cost efficiency through storage consolidation:** Azure Container Storage reduces storage cost and management overhead by consolidating many smaller volumes under a single SAN. Elastic SAN tiered provisioning also helps reduce overprovisioning and lowers total cost of ownership.
 - **Kubernetes-native volume orchestration:** Create StorageClass objects and persistent volumes, and manage the full lifecycle of volumes including provisioning, expansion, deletion, and snapshots using `kubectl` commands.
 - **Open source and community-driven:** Azure Container Storage is developed as an open-source project. You can install it through an AKS extension, as described in the [tutorial](install-container-storage-aks.md), or through Helm using the [local-csi-driver](https://github.com/Azure/local-csi-driver) repository.

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

@@ -46,7 +46,7 @@ A **major release** introduces significant changes, often including new features
 
 ### Improvements and issues that are fixed
 
-- Addressed a vulnerability where full customer pod details including potentially sensitive data passed through environment variables were being logged. Logging has now been restricted to pod name only to prevent exposure of sensitive information.
+- Address a vulnerability where full customer pod details, including potentially sensitive data, pass through environment variables and are logged. The system now logs only the pod name to prevent exposure of sensitive information.
 
 ## Version 2.0.0