[ACA] [371940] Add subPath documentation.

Author: v-jaswel

articles/container-apps/storage-mounts-azure-files.md

@@ -6,7 +6,7 @@ author: craigshoemaker
 ms.service: azure-container-apps
 ms.custom: devx-track-azurecli
 ms.topic: tutorial
-ms.date: 02/03/2025
+ms.date: 02/26/2025
 ms.author: cshoe
 ---
 
@@ -438,30 +438,35 @@ Now you can update the container app configuration to support the storage mount.
 
 1. Open *app.yaml* in a code editor.
 
-1. Replace the `volumes: null` definition in the `template` section with a `volumes:` definition referencing the storage volume.  The template section should look like the following:
+1. Replace the `volumes: null` definition in the `template` section with a `volumes:` definition referencing the storage volume. The template section should look like the following:
 
     ```yml
     template:
-      volumes:
-      - name: my-azure-file-volume
-        storageName: mystoragemount
-        storageType: AzureFile
       containers:
       - image: nginx
+        imageType: ContainerImage
         name: my-container-app
-        volumeMounts:
-        - volumeName: my-azure-file-volume
-          mountPath: /var/log/nginx
         resources:
           cpu: 0.5
-          ephemeralStorage: 3Gi
+          ephemeralStorage: 2Gi
           memory: 1Gi
+        volumeMounts:
+        - volumeName: my-azure-file-volume
+          mountPath: /var/log/nginx
       initContainers: null
       revisionSuffix: ''
       scale:
+        cooldownPeriod: 300
         maxReplicas: 1
         minReplicas: 1
+        pollingInterval: 30
         rules: null
+      serviceBinds: null
+      terminationGracePeriodSeconds: null
+      volumes:
+      - name: my-azure-file-volume
+        storageName: mystoragemount
+        storageType: AzureFile
     ```
 
     The new `template.volumes` section includes the following properties.
@@ -540,78 +545,50 @@ Now that the storage mount is established, you can manipulate files in Azure Sto
 
     ---
 
-    This command may take a moment to open the remote shell. Once the shell is ready, you can interact with the storage mount via file system commands.
+    This command may take a moment to open the remote shell. Once the shell is ready, you can interact with the storage mount via file system commands. For more information see [Connect to a container console in Azure Container Apps](/azure/container-apps/container-console).
 
-1. Change into the nginx */var/log/nginx* folder.
+1. Run the following command to see the mounted file share.
 
-    # [Bash](#tab/bash)
+    ```sh
+    findmnt | grep nginx
+    ```
 
-    ```bash
-    cd /var/log/nginx
+    You see output similar to the following.
+    
+    ```
+    `-/var/log/nginx                      //<STORAGE_ACCOUNT_NAME>.file.core.windows.net/<STORAGE_SHARE_NAME>      cifs    rw,relatime,vers=3.1.1,cache=strict,username=<STORAGE_ACCOUNT_NAME>,uid=0,forceuid,gid=0,forcegid,addr=57.150.154.70,file_mode=0777,dir_mode=0777,soft,persistenthandles,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,bsize=1048576,echo_interval=30,actimeo=1,closetimeo=1
     ```
 
-    # [PowerShell](#tab/powershell)
+1. Change into the nginx */var/log/nginx* folder.
 
-    ```powershell
+    ```sh
     cd /var/log/nginx
     ```
 
-    ---
-
 1. Return to the browser and navigate to the website and refresh the page a few times.
 
     The requests made to the website create a series of log stream entries.
 
 1. Return to your terminal and list the values of the `/var/log/nginx` folder.
 
-    # [Bash](#tab/bash)
-
-    ```bash
+    ```sh
     ls
     ```
 
-    # [PowerShell](#tab/powershell)
-
-    ```powershell
-    ls
-    ```
-
-    ---
-
     Note how the *access.log* and *error.log* files appear in this folder. These files are written to the Azure Files mount in your Azure Storage share created in the previous steps.
 
 1. View the contents of the *access.log* file.
 
-    # [Bash](#tab/bash)
-
-    ```bash
+    ```sh
     cat access.log
     ```
 
-    # [PowerShell](#tab/powershell)
-
-    ```powershell
-    type access.log
-    ```
-
-    ---
-
 1. Exit out of the container's interactive shell to return to your local terminal session.
 
-    # [Bash](#tab/bash)
-
-    ```bash
-    exit
-    ```
-
-    # [PowerShell](#tab/powershell)
-
-    ```powershell
+    ```sh
     exit
     ```
 
-    ---
-
 1. Now, you can view the files in the Azure portal to verify they exist in your Azure Storage account. Print the name of your randomly generated storage account.
 
     # [Bash](#tab/bash)

articles/container-apps/storage-mounts.md

@@ -6,7 +6,7 @@ author: craigshoemaker
 ms.service: azure-container-apps
 ms.custom: devx-track-azurecli
 ms.topic: conceptual
-ms.date: 02/25/2025
+ms.date: 02/26/2025
 ms.author: cshoe
 zone_pivot_groups: arm-azure-cli-portal
 ---
@@ -326,7 +326,7 @@ For a step-by-step tutorial on mounting an SMB file share, refer to [Create an A
     - For each container in the template that you want to mount Azure Files storage, define a volume mount in the `volumeMounts` array of the container definition.
         - The `volumeName` is the name defined in the `volumes` array.
         - The `mountPath` is the path in the container to mount the volume.
-        - The `subPath` (optional) is the path in the volume to mount. If not specified, the volume root is mounted. For more information see [using subPath](https://kubernetes.io/docs/concepts/storage/volumes/#using-subpath).
+        - The `subPath` is the path in the volume to mount. If not specified, the volume root is mounted. For more information see (#sub-path).
 
     # [SMB](#tab/smb)
 
@@ -586,7 +586,7 @@ The following ARM template snippets demonstrate how to add an Azure Files share
     - For each container in the template that you want to mount Azure Files storage, define a volume mount in the `volumeMounts` array of the container definition.
         - The `volumeName` is the name defined in the `volumes` array.
         - The `mountPath` is the path in the container to mount the volume.
-        - The `subPath` (optional) is the path in the volume to mount. If not specified, the volume root is mounted. For more information see [using subPath](https://kubernetes.io/docs/concepts/storage/volumes/#using-subpath).
+        - The `subPath` (optional) is the path in the volume to mount. If not specified, the volume root is mounted. For more information see (#sub-path).
 
 See the [ARM template API specification](azure-resource-manager-api-spec.md) for a full example.
 
@@ -656,10 +656,25 @@ To configure a volume mount for Azure Files storage in the Azure portal, add a f
 
 1. In **Mount path**, enter the absolute path in the container to mount the volume.
 
-1. In **Sub path (optional)**, enter the path in the volume to mount. If not specified, the volume root is mounted. For more information see [using subPath](https://kubernetes.io/docs/concepts/storage/volumes/#using-subpath).
+1. In **Sub path (optional)**, enter the path in the volume to mount. If not specified, the volume root is mounted. For more information see (#sub-path).
 
 1. Select **Save** to save changes and exit the context pane.
 
 1. Select **Create** to create the new revision.
 
 ::: zone-end
+
+### Sub path
+
+When mounting a file share from Azure Files, in addition to the mount path, you can also specify a sub path.
+
+- The mount path is the path in the container where you want to mount the volume.
+- The sub path is the path in the volume you want to mount.
+- The sub path is optional. If not specified, the volume root is mounted.
+- The sub path should be a relative path from the volume root. The sub path should not start with `/`. Specifying a sub path that starts with `/` might prevent your container app from starting up.
+- The sub path can refer to either a folder or a file in the volume.
+    - If the sub path refers to a folder in the volume, the mount path should refer to an empty folder in the container.
+    - If the sub path refers to a file in the volume, the mount path should refer to a file that does not exist in the container. For example, if the sub path is `my-volume-folder/my-volume-file`, and the mount path is `/my-container-folder/my-container-file`, the folder `/my-container-folder` should exist in the container, but should not already contain the file `my-container-file`.
+- If the sub path contains a trailing `/`, whether it refers to a folder or file, the trailing `/` is ignored.
+
+For more information see [using subPath](https://kubernetes.io/docs/concepts/storage/volumes/#using-subpath).