Skip to content

Commit 44f14c9

Browse files
authored
Merge pull request #18210 from MicrosoftDocs/main
6/16/2025 AM Publish
2 parents 8fa5d1f + 938a130 commit 44f14c9

File tree

4 files changed

+34
-71
lines changed

4 files changed

+34
-71
lines changed

AKS-Arc/concepts-storage.md

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Concepts - Storage options for applications in AKS enabled by Azure Arc
33
description: Storage options for applications in AKS enabled by Azure Arc.
44
author: sethmanheim
55
ms.topic: conceptual
6-
ms.date: 06/24/2024
6+
ms.date: 06/16/2025
77
ms.author: sethm
88
ms.lastreviewed: 1/14/2022
99
ms.reviewer: abha
@@ -112,6 +112,23 @@ volumeMounts:
112112
name: k-dir
113113
```
114114

115+
## Secure pod access to mounted volumes
116+
117+
For your applications to run correctly, pods should run as a defined user or group and not as *root*. The `securityContext` for a pod or container lets you define settings such as *fsGroup* to assume the appropriate permissions on the mounted volumes.
118+
119+
**fsGroup** is a field within the `securityContext` of a Kubernetes pod specification. It defines a supplemental group ID that Kubernetes assigns to all processes in the pod, and recursively to the files in mounted volumes. This ensures that the pod has the correct group-level access to shared storage volumes.
120+
121+
When a volume is mounted, Kubernetes changes the ownership of the volume's contents to match the **fsGroup** value. This is particularly useful when containers run as non-root users and need write access to shared volumes.
122+
123+
The following example YAML shows the **fsgroup** value:
124+
125+
```yaml
126+
securityContext:
127+
  fsGroup: 2000
128+
```
129+
130+
In this example, all files in mounted volumes are accessible by GID 2000.
131+
115132
## Next steps
116133

117134
- [Use the AKS on Azure Local disk Container Storage Interface (CSI) drivers](./container-storage-interface-disks.md).

AKS-Arc/container-storage-interface-files.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Use Container Storage Interface (CSI) file drivers in AKS enabled by Azur
33
description: Learn how to use Container Storage Interface (CSI) drivers to manage files in AKS Arc.
44
author: sethmanheim
55
ms.topic: how-to
6-
ms.date: 08/20/2024
6+
ms.date: 06/16/2025
77
ms.author: sethm
88
ms.lastreviewed: 01/14/2022
99
ms.reviewer: abha
@@ -31,7 +31,7 @@ If multiple nodes need concurrent access to the same storage volumes in AKS Arc,
3131

3232
### [AKS on Azure Local](#tab/local)
3333

34-
1. Make sure the SMB driver is deployed. The SMB CSI driver is installed by default when you create a Kubernetes cluster using the `az aksarc create` command. If you create a Kubernetes cluster by using the Azure portal or using the `az aksarc create` command with `--disable-smb-driver`, you must enable the SMB driver on this cluster using the `az aksarc update` command:
34+
1. Make sure the SMB driver is deployed. The SMB CSI driver is installed by default when you create a Kubernetes cluster using the `az aksarc create` command. If you create a Kubernetes cluster by using the Azure portal, Azure Resource Manager (ARM) template, or Terraform, or by using the `az aksarc create` command with `--disable-smb-driver`, you must enable the SMB driver on this cluster using the `az aksarc update` command:
3535

3636
```azurecli
3737
az aksarc update -n $aksclustername -g $resource_group --enable-smb-driver
@@ -78,7 +78,7 @@ If multiple nodes need concurrent access to the same storage volumes in AKS Arc,
7878
7979
### [AKS on Azure Local](#tab/local)
8080
81-
1. Make sure the NFS driver is deployed. The NFS CSI driver is installed by default when you create a Kubernetes cluster using the `az aksarc create` command. If you create a Kubernetes cluster by using the Azure portal or using the `az aksarc create` command with `--disable-nfs-driver`, you must enable the the NFS driver on this cluster using the `az aksarc update` command:
81+
1. Make sure the NFS driver is deployed. The NFS CSI driver is installed by default when you create a Kubernetes cluster using the `az aksarc create` command. If you create a Kubernetes cluster by using the Azure portal, Azure Resource Manager (ARM) template, or Terraform, or by using the `az aksarc create` command with `--disable-nfs-driver`, you must enable the the NFS driver on this cluster using the `az aksarc update` command:
8282

8383
```azurecli
8484
az aksarc update -n $aksclustername -g $resource_group --enable-nfs-driver

0 commit comments

Comments
 (0)