Merge pull request #223778 from zioproto/patch-2

Note spec.capacity.storage is required but unused

Author: prmerger-automator[bot]

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

@@ -91,7 +91,7 @@ The following example demonstrates how to mount a Blob storage container as a pe
       name: pv-blob
     spec:
       capacity:
-        storage: 10Gi
+        storage: 1Pi
       accessModes:
         - ReadWriteMany
       persistentVolumeReclaimPolicy: Retain  # If set as "Delete" container would be removed after pvc deletion
@@ -108,6 +108,8 @@ The following example demonstrates how to mount a Blob storage container as a pe
           containerName: containerName
           protocol: nfs
     ```
+    > [!NOTE]
+    > While the [Kubernetes API](https://github.com/kubernetes/kubernetes/blob/release-1.26/pkg/apis/core/types.go#L303-L306) **capacity** attribute is mandatory, this value isn't used by the Azure Blob storage CSI driver because you can flexibly write data until you reach your storage account's capacity limit. The value of the `capacity` attribute is used only for size matching between *PersistentVolumes* and *PersistenVolumeClaims*. We recommend using a fictitious high value. The pod sees a mounted volume with a fictitious size of 5 Petabytes.
 
 2. Run the following command to create the persistent volume using the `kubectl create` command referencing the YAML file created earlier:
 
@@ -222,7 +224,7 @@ Kubernetes needs credentials to access the Blob storage container created earlie
     kubectl create -f pvc-blobfuse.yaml
     ```
 
-## Use the persistence volume
+## Use the persistent volume
 
 The following YAML creates a pod that uses the persistent volume or persistent volume claim named **pvc-blob** created earlier, to mount the Azure Blob storage at the `/mnt/blob' path.