Skip to content

Commit 9aa049d

Browse files
committed
refinements
1 parent 15c5eb8 commit 9aa049d

File tree

1 file changed

+24
-20
lines changed

1 file changed

+24
-20
lines changed

articles/storage/files/azure-kubernetes-service-workloads.md

Lines changed: 24 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to use Azure file shares for Azure Kubernetes Service (AK
44
author: khdownie
55
ms.service: azure-file-storage
66
ms.topic: concept-article
7-
ms.date: 06/30/2025
7+
ms.date: 07/02/2025
88
ms.author: kendownie
99
# Customer intent: "As a Kubernetes administrator, I want to implement Azure Files for my Azure Kubernetes Service (AKS) workloads requiring persistent, shared storage, so that I can better support my organization's containerized applications."
1010
---
@@ -15,51 +15,52 @@ Azure Files provides fully managed file shares in the cloud that are accessible
1515

1616
## What is Azure Kubernetes Service?
1717

18-
Azure Kubernetes Service (AKS) is a managed Kubernetes service that simplifies deploying, managing, and scaling containerized applications using Kubernetes on Azure. AKS reduces the complexity and operational overhead of managing Kubernetes by offloading much of that responsibility to Azure. As a hosted Kubernetes service, Azure handles critical tasks like health monitoring and maintenance, while you focus on your application workloads.
18+
Azure Kubernetes Service is a managed Kubernetes service that simplifies deploying, managing, and scaling containerized applications using Kubernetes on Azure. It reduces the complexity and operational overhead of managing Kubernetes by offloading much of that responsibility to Azure. As a hosted Kubernetes service, AKS handles critical tasks like health monitoring and maintenance, while you focus on your application workloads.
1919

20-
## Why Azure Files for Azure Kubernetes Service?
20+
## Why Azure Files for AKS?
2121

22-
Azure Files is an ideal storage solution for AKS workloads due to several advantages:
22+
The combination of persistent shared storage, Kubernetes-native integration, and enterprise-grade performance and security makes Azure Files an excellent choice for stateful applications, shared data scenarios, and complex multi-pod architectures in AKS environments. Whether you're deploying content management systems, implementing centralized logging, or building data processing pipelines, Azure Files offers the flexibility and reliability needed to support your AKS infrastructure at scale.
2323

2424
### Persistent shared storage
2525

2626
Unlike local storage that's tied to individual nodes, Azure Files provides persistent storage that survives pod restarts, node failures, and cluster scaling events. Multiple pods across different nodes can simultaneously access the same file share, enabling shared data scenarios and stateful applications.
2727

2828
### Kubernetes native integration
2929

30-
Azure Files integrates seamlessly with Kubernetes through the Container Storage Interface (CSI) driver, allowing you to provision and manage file shares using standard Kubernetes constructs like PersistentVolumes (PV) and PersistentVolumeClaims (PVC). The CSI driver handles all the complexity of Azure API interactions, authentication, and mount operations, providing a native Kubernetes experience for storage management.
30+
Azure Files integrates seamlessly with Kubernetes through the Container Storage Interface (CSI) driver, allowing you to provision and manage file shares using standard Kubernetes constructs like persistent volumes (PV) and persistent volume claims (PVC). The CSI driver handles all the complexity of Azure API interactions, authentication, and mount operations, providing a native Kubernetes experience for storage management.
3131

32-
### Multiple performance tiers
32+
### SSD file shares for optimal performance
3333

34-
Azure Files offers multiple performance tiers to match your workload requirements:
34+
Azure Files offers two types of storage media:
3535

3636
- **HDD (Standard)**: Cost-effective for general-purpose workloads
3737
- **SSD (Premium)**: High-performance SSD-backed storage for I/O intensive applications
38-
- **Transaction optimized**: Optimized for workloads with high transaction rates
38+
39+
For optimal performance, we recommend using SSD file shares deployed in the same Azure region as your AKS cluster. This minimizes latency and maximizes throughput for file operations.
3940

4041
### Protocol support
4142

4243
Support for both NFS and SMB protocols ensures compatibility with a wide range of applications and operating systems, including Linux and Windows containers.
4344

4445
### Security and compliance
4546

46-
Azure Files provides enterprise-grade security features including encryption at rest, encryption in transit, Microsoft Entra ID integration, and compliance with industry standards.
47+
Azure Files provides essential security features including encryption at rest, encryption in transit, Microsoft Entra ID integration, and compliance with industry standards.
4748

4849
## Understanding the Azure Files CSI driver
4950

50-
The Azure Files Container Storage Interface (CSI) driver is a critical component that enables seamless integration between Azure Files and Kubernetes clusters, including AKS. The CSI specification provides a standardized interface for storage systems to expose their capabilities to containerized workloads, and the Azure Files CSI driver implements this specification specifically for Azure Files.
51+
The Azure Files Container Storage Interface (CSI) driver is a critical component that enables seamless integration between Azure Files and Kubernetes clusters, including AKS. The CSI specification provides a standardized interface for storage systems to expose their capabilities to containerized workloads, and the Azure Files CSI driver implements this specification specifically for Azure Files. For more information, see [Use Azure Files CSI driver in AKS](/azure/aks/azure-files-csi).
5152

5253
### How the CSI driver works
5354

5455
The Azure Files CSI driver operates through several key components:
5556

5657
- **CSI driver pod**: Runs as a DaemonSet on each node in the AKS cluster, responsible for mounting and unmounting Azure file shares
57-
- **CSI controller**: Manages the lifecycle of Azure Files shares, including creation, deletion, and volume expansion
58+
- **CSI controller**: Manages the lifecycle of Azure file shares, including creation, deletion, and volume expansion
5859
- **Storage classes**: Define the parameters and policies for dynamic provisioning of Azure file shares
59-
- **Persistent volumes (PV)**: Represent the actual Azure Files shares in Kubernetes
60-
- **Persistent volume claims (PVC)**: User requests for storage that are bound to persistent volumes
60+
- **Persistent volumes**: Represent the actual Azure file shares in Kubernetes
61+
- **Persistent volume claims**: User requests for storage that are bound to persistent volumes
6162

62-
When a pod requests storage through a PVC, the CSI driver coordinates with Azure APIs to either create a new Azure file share (dynamic provisioning) or connect to an existing share (static provisioning). The driver then mounts the share into the pod's filesystem namespace, making it accessible to applications.
63+
When a pod requests storage through a persistent volume claim, the CSI driver coordinates with Azure APIs to either create a new Azure file share (dynamic provisioning) or connect to an existing share (static provisioning). The driver then mounts the share into the pod's filesystem namespace, making it accessible to applications.
6364

6465
### CSI driver capabilities
6566

@@ -116,7 +117,7 @@ Azure Files is particularly useful for:
116117
- **Certificate distribution**: Centrally manage and distribute SSL/TLS certificates.
117118
- **Shared libraries**: Store common libraries or binaries accessed by multiple applications.
118119
119-
This YAML example creates a PVC for shared configuration storage and a deployment that mounts this storage across multiple pod replicas:
120+
This YAML example creates a persistent volume claim for shared configuration storage and a deployment that mounts this storage across multiple pod replicas:
120121
121122
```yaml
122123
apiVersion: v1
@@ -216,7 +217,7 @@ Azure Files CSI driver supports both static and dynamic provisioning through Kub
216217
217218
With dynamic provisioning, storage is automatically created when a persistent volume claim is created.
218219
219-
This YAML defines a StorageClass for dynamic provisioning of premium Azure Files shares with SMB protocol and specific mount options:
220+
This YAML defines a storage class for dynamic provisioning of SSD (premium) Azure file shares with SMB protocol and specific mount options:
220221
221222
```yaml
222223
apiVersion: storage.k8s.io/v1
@@ -240,9 +241,9 @@ mountOptions:
240241
241242
### Static provisioning
242243
243-
For existing Azure Files shares, you can create persistent volumes that reference pre-created storage.
244+
For existing Azure file shares, you can create persistent volumes that reference pre-created storage.
244245
245-
This YAML example shows how to create a Persistent Volume that references an existing Azure file share using static provisioning:
246+
This YAML example shows how to create a persistent volume that references an existing Azure file share using static provisioning:
246247
247248
```yaml
248249
apiVersion: v1
@@ -267,8 +268,7 @@ spec:
267268
protocol: smb
268269
```
269270
270-
271-
## Optimize mount options
271+
## Recommended mount options
272272
273273
This YAML example shows optimized mount options for Azure Files to improve performance and compatibility. However, you should configure mount options to optimize performance for your specific use case.
274274
@@ -310,3 +310,7 @@ parameters:
310310
networkEndpointType: privateEndpoint
311311
```
312312
313+
## See also
314+
315+
- [Use Azure Files CSI driver in AKS](/azure/aks/azure-files-csi)
316+
- [Create and use a volume with Azure Files in AKS](/azure/aks/azure-csi-files-storage-provision)

0 commit comments

Comments
 (0)