You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/aks/azure-files-csi.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,12 +25,14 @@ In addition to the original in-tree driver features, Azure Files CSI driver supp
25
25
26
26
- Network File System (NFS) version 4.1
27
27
-[Private endpoint][private-endpoint-overview]
28
-
- Creating large mount of file shares in parallel
28
+
- Creating large mount of file shares in parallel.
29
29
30
30
## Use a persistent volume with Azure Files
31
31
32
32
A [persistent volume (PV)][persistent-volume] represents a piece of storage that's provisioned for use with Kubernetes pods. A PV can be used by one or many pods and can be dynamically or statically provisioned. If multiple pods need concurrent access to the same storage volume, you can use Azure Files to connect by using the [Server Message Block (SMB)][smb-overview] or [NFS protocol][nfs-overview]. This article shows you how to dynamically create an Azure Files share for use by multiple pods in an AKS cluster. For static provisioning, see [Manually create and use a volume with an Azure Files share][azure-files-pvc-manual].
33
33
34
+
With Azure Files shares, there is no limit as to how many can be mounted on a node.
35
+
34
36
For more information on Kubernetes volumes, see [Storage options for applications in AKS][concepts-storage].
35
37
36
38
## Dynamically create Azure Files PVs by using the built-in storage classes
Copy file name to clipboardExpand all lines: articles/aks/operator-best-practices-storage.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ titleSuffix: Azure Kubernetes Service
4
4
description: Learn the cluster operator best practices for storage, data encryption, and backups in Azure Kubernetes Service (AKS)
5
5
services: container-service
6
6
ms.topic: conceptual
7
-
ms.date: 03/10/2021
7
+
ms.date: 11/30/2022
8
8
9
9
---
10
10
@@ -26,7 +26,8 @@ This best practices article focuses on storage considerations for cluster operat
26
26
>
27
27
> Understand the needs of your application to pick the right storage. Use high performance, SSD-backed storage for production workloads. Plan for network-based storage when you need multiple concurrent connections.
28
28
29
-
Applications often require different types and speeds of storage. Determine the most appropriate storage type by asking the following questions.
29
+
Applications often require different types and speeds of storage. Determine the most appropriate storage type by asking the following questions.
30
+
30
31
* Do your applications need storage that connects to individual pods?
31
32
* Do your applications need storage shared across multiple pods?
32
33
* Is the storage for read-only access to data?
@@ -40,18 +41,18 @@ The following table outlines the available storage types and their capabilities:
40
41
| Structured app data | Azure Disks | Yes | No | No | Yes |
41
42
| Unstructured data, file system operations |[BlobFuse][blobfuse]| Yes | Yes | Yes | No |
42
43
43
-
AKS provides two primary types of secure storage for volumes backed by Azure Disks or Azure Files. Both use the default Azure Storage Service Encryption (SSE) that encrypts data at rest. Disks cannot be encrypted using Azure Disk Encryption at the AKS node level.
44
+
AKS provides two primary types of secure storage for volumes backed by Azure Disks or Azure Files. Both use the default Azure Storage Service Encryption (SSE) that encrypts data at rest. Disks cannot be encrypted using Azure Disk Encryption at the AKS node level. With Azure Files shares, there is no limit as to how many can be mounted on a node.
44
45
45
46
Both Azure Files and Azure Disks are available in Standard and Premium performance tiers:
46
47
47
48
-*Premium* disks
48
-
- Backed by high-performance solid-state disks (SSDs).
49
+
- Backed by high-performance solid-state disks (SSDs).
49
50
- Recommended for all production workloads.
50
51
-*Standard* disks
51
52
- Backed by regular spinning disks (HDDs).
52
53
- Good for archival or infrequently accessed data.
53
54
54
-
Understand the application performance needs and access patterns to choose the appropriate storage tier. For more information about Managed Disks sizes and performance tiers, see [Azure Managed Disks overview][managed-disks]
55
+
Understand the application performance needs and access patterns to choose the appropriate storage tier. For more information about Managed Disks sizes and performance tiers, see [Azure Managed Disks overview][managed-disks].
55
56
56
57
### Create and use storage classes to define application needs
0 commit comments