Skip to content

Commit 1cb8469

Browse files
Merge pull request #220097 from MGoedtel/task28377
Make point no limit for CSI Azure Files shares
2 parents 000d4c9 + 4df36d9 commit 1cb8469

File tree

2 files changed

+9
-6
lines changed

2 files changed

+9
-6
lines changed

articles/aks/azure-files-csi.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,12 +25,14 @@ In addition to the original in-tree driver features, Azure Files CSI driver supp
2525

2626
- Network File System (NFS) version 4.1
2727
- [Private endpoint][private-endpoint-overview]
28-
- Creating large mount of file shares in parallel
28+
- Creating large mount of file shares in parallel.
2929

3030
## Use a persistent volume with Azure Files
3131

3232
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].
3333

34+
With Azure Files shares, there is no limit as to how many can be mounted on a node.
35+
3436
For more information on Kubernetes volumes, see [Storage options for applications in AKS][concepts-storage].
3537

3638
## Dynamically create Azure Files PVs by using the built-in storage classes

articles/aks/operator-best-practices-storage.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ titleSuffix: Azure Kubernetes Service
44
description: Learn the cluster operator best practices for storage, data encryption, and backups in Azure Kubernetes Service (AKS)
55
services: container-service
66
ms.topic: conceptual
7-
ms.date: 03/10/2021
7+
ms.date: 11/30/2022
88

99
---
1010

@@ -26,7 +26,8 @@ This best practices article focuses on storage considerations for cluster operat
2626
>
2727
> 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.
2828
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+
3031
* Do your applications need storage that connects to individual pods?
3132
* Do your applications need storage shared across multiple pods?
3233
* Is the storage for read-only access to data?
@@ -40,18 +41,18 @@ The following table outlines the available storage types and their capabilities:
4041
| Structured app data | Azure Disks | Yes | No | No | Yes |
4142
| Unstructured data, file system operations | [BlobFuse][blobfuse] | Yes | Yes | Yes | No |
4243

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.
4445

4546
Both Azure Files and Azure Disks are available in Standard and Premium performance tiers:
4647

4748
- *Premium* disks
48-
- Backed by high-performance solid-state disks (SSDs).
49+
- Backed by high-performance solid-state disks (SSDs).
4950
- Recommended for all production workloads.
5051
- *Standard* disks
5152
- Backed by regular spinning disks (HDDs).
5253
- Good for archival or infrequently accessed data.
5354

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].
5556

5657
### Create and use storage classes to define application needs
5758

0 commit comments

Comments
 (0)