Skip to content

Commit 2a0d90e

Browse files
Merge pull request #236307 from MGoedtel/bug87296
Clarify storage tier for CSI Disk StorageClass
2 parents eede45e + 289b65e commit 2a0d90e

File tree

2 files changed

+8
-8
lines changed

2 files changed

+8
-8
lines changed

articles/aks/azure-disk-csi.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
2-
title: Use Container Storage Interface (CSI) driver for Azure Disks on Azure Kubernetes Service (AKS)
3-
description: Learn how to use the Container Storage Interface (CSI) driver for Azure Disks in an Azure Kubernetes Service (AKS) cluster.
2+
title: Use Container Storage Interface (CSI) driver for Azure Disk on Azure Kubernetes Service (AKS)
3+
description: Learn how to use the Container Storage Interface (CSI) driver for Azure Disk in an Azure Kubernetes Service (AKS) cluster.
44
ms.topic: article
55
ms.date: 04/19/2023
66
---
77

8-
# Use the Azure Disks Container Storage Interface (CSI) driver in Azure Kubernetes Service (AKS)
8+
# Use the Azure Disk Container Storage Interface (CSI) driver in Azure Kubernetes Service (AKS)
99

10-
The Azure Disks Container Storage Interface (CSI) driver is a [CSI specification](https://github.com/container-storage-interface/spec/blob/master/spec.md)-compliant driver used by Azure Kubernetes Service (AKS) to manage the lifecycle of Azure Disks.
10+
The Azure Disks Container Storage Interface (CSI) driver is a [CSI specification](https://github.com/container-storage-interface/spec/blob/master/spec.md)-compliant driver used by Azure Kubernetes Service (AKS) to manage the lifecycle of Azure Disk.
1111

1212
The CSI is a standard for exposing arbitrary block and file storage systems to containerized workloads on Kubernetes. By adopting and using CSI, AKS now can write, deploy, and iterate plug-ins to expose new or improve existing storage systems in Kubernetes. Using CSI drivers in AKS avoids having to touch the core Kubernetes code and wait for its release cycles.
1313

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Best practices for storage and backup
33
titleSuffix: Azure Kubernetes Service
44
description: Learn the cluster operator best practices for storage, data encryption, and backups in Azure Kubernetes Service (AKS)
55
ms.topic: conceptual
6-
ms.date: 11/30/2022
6+
ms.date: 04/28/2023
77

88
---
99

@@ -22,7 +22,7 @@ This best practices article focuses on storage considerations for cluster operat
2222
## Choose the appropriate storage type
2323

2424
> **Best practice guidance**
25-
>
25+
>
2626
> 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.
2727
2828
Applications often require different types and speeds of storage. Determine the most appropriate storage type by asking the following questions.
@@ -51,6 +51,8 @@ Both Azure Files and Azure Disks are available in Standard and Premium performan
5151
- Backed by regular spinning disks (HDDs).
5252
- Good for archival or infrequently accessed data.
5353

54+
While the default storage tier for the Azure Disk CSI driver is Premium SSD, your custom StorageClass can use Premium SSD, Standard SSD, or Standard HDD.
55+
5456
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].
5557

5658
### Create and use storage classes to define application needs
@@ -89,8 +91,6 @@ Work with your application development team to understand their storage capacity
8991
9092
For more information about available VM sizes, see [Sizes for Linux virtual machines in Azure][vm-sizes].
9193

92-
93-
9494
## Dynamically provision volumes
9595

9696
> **Best practice guidance**

0 commit comments

Comments
 (0)