Merge pull request #222382 from andyzhangx/patch-60

Update azure-files-volume.md

Author: prmerger-automator[bot]

articles/aks/azure-blob-csi.md

@@ -3,7 +3,7 @@ title: Use Container Storage Interface (CSI) driver for Azure Blob storage on Az
 description: Learn how to use the Container Storage Interface (CSI) driver for Azure Blob storage in an Azure Kubernetes Service (AKS) cluster.
 services: container-service
 ms.topic: article
-ms.date: 11/30/2022
+ms.date: 12/27/2022
 author: mgoedtel
 
 ---
@@ -23,7 +23,7 @@ Mounting Azure Blob storage as a file system into a container or pod, enables yo
 The data on the object storage can be accessed by applications using BlobFuse or Network File System (NFS) 3.0 protocol. Before the introduction of the Azure Blob storage CSI driver, the only option was to manually install an unsupported driver to access Blob storage from your application running on AKS. When the Azure Blob storage CSI driver is enabled on AKS, there are two built-in storage classes: *azureblob-fuse-premium* and *azureblob-nfs-premium*.
 
 > [!NOTE]
-> Azure Blob CSI driver only supports NFS 3.0 protocol for Kubernetes versions 1.25 (preview) on AKS.
+> Azure Blob CSI driver only supports NFS 3.0 protocol for Kubernetes versions 1.25 on AKS.
 
 To create an AKS cluster with CSI drivers support, see [CSI drivers on AKS][csi-drivers-aks]. To learn more about the differences in access between each of the Azure storage types using the NFS protocol, see [Compare access to Azure Files, Blob Storage, and Azure NetApp Files with NFS][compare-access-with-nfs].
 

articles/aks/azure-csi-blob-storage-static.md

@@ -4,7 +4,7 @@ titleSuffix: Azure Kubernetes Service
 description: Learn how to create a static persistent volume with Azure Blob storage for use with multiple concurrent pods in Azure Kubernetes Service (AKS)
 services: container-service
 ms.topic: article
-ms.date: 07/21/2022
+ms.date: 12/27/2022
 
 ---
 
@@ -22,12 +22,13 @@ For more information on Kubernetes volumes, see [Storage options for application
 
 - If you don't have a storage account that supports the NFS v3 protocol, review [NFS v3 support with Azure Blob storage][azure-blob-storage-nfs-support].
 
-- [Enable the Blob storage CSI driver][enable-blob-csi-driver] (preview) on your AKS cluster.
+- [Enable the Blob storage CSI driver][enable-blob-csi-driver] on your AKS cluster.
 
 ## Static provisioning parameters
 
 |Name | Description | Example | Mandatory | Default value|
 |--- | --- | --- | --- | ---|
+|volumeHandle | Specify a value the driver can use to uniquely identify the storage blob container in the cluster. | A recommended way to produce a unique value is to combine the globally unique storage account name and container name: {account-name}_{container-name}. Note: The # character is reserved for internal use and can't be used in a volume handle. | Yes ||
 |volumeAttributes.resourceGroup | Specify Azure resource group name. | myResourceGroup | No | If empty, driver will use the same resource group name as current cluster.|
 |volumeAttributes.storageAccount | Specify existing Azure storage account name. | storageAccountName | Yes ||
 |volumeAttributes.containerName | Specify existing container name. | container | Yes ||
@@ -98,8 +99,8 @@ The following example demonstrates how to mount a Blob storage container as a pe
       csi:
         driver: blob.csi.azure.com
         readOnly: false
-        # make sure this volumeid is unique in the cluster
-        # `#` is not allowed in self defined volumeHandle
+        # make sure volumeid is unique for every identical storage blob container in the cluster
+        # character `#` is reserved for internal use and cannot be used in volumehandle
         volumeHandle: unique-volumeid
         volumeAttributes:
           resourceGroup: resourceGroupName
@@ -182,8 +183,8 @@ Kubernetes needs credentials to access the Blob storage container created earlie
       csi:
         driver: blob.csi.azure.com
         readOnly: false
-        # make sure this volumeid is unique in the cluster
-        # `#` is not allowed in self defined volumeHandle
+        # make sure volumeid is unique for every identical storage blob container in the cluster
+        # character `#` is reserved for internal use and cannot be used in volumehandle
         volumeHandle: unique-volumeid
         volumeAttributes:
           containerName: containerName

articles/aks/azure-files-volume.md

@@ -4,7 +4,7 @@ titleSuffix: Azure Kubernetes Service
 description: Learn how to manually create a volume with Azure Files for use with multiple concurrent pods in Azure Kubernetes Service (AKS)
 services: container-service
 ms.topic: article
-ms.date: 12/12/2022
+ms.date: 12/26/2022
 
 
 #Customer intent: As a developer, I want to learn how to manually create and attach storage using Azure Files to a pod in AKS.
@@ -101,7 +101,7 @@ spec:
       volumeAttributes:
         secretName: azure-secret  # required
         shareName: aksshare  # required
-        mountOptions: "dir_mode=0777,file_mode=0777,cache=strict,actimeo=30"  # optional
+        mountOptions: "dir_mode=0777,file_mode=0777,cache=strict,actimeo=30,nosharesock"  # optional
 ```
 
 Use the `kubectl` command to create the pod.
@@ -133,7 +133,7 @@ spec:
   csi:
     driver: file.csi.azure.com
     readOnly: false
-    volumeHandle: unique-volumeid  # make sure this volumeid is unique in the cluster
+    volumeHandle: unique-volumeid  # make sure volumeid is unique for every identical share in the cluster
     volumeAttributes:
       resourceGroup: EXISTING_RESOURCE_GROUP_NAME  # optional, only set this when storage account is not in the same resource group as agent node
       shareName: aksshare