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/storage/container-storage/install-container-storage-aks.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -140,5 +140,5 @@ After installation, configure `kubectl` to connect to your cluster and verify th
140
140
141
141
## Next step
142
142
143
-
- [Create generic ephemeral volume with local NVMe](use-container-storage-with-local-disk.md)
143
+
- [Use Azure Container Storage with local NVMe](use-container-storage-with-local-disk.md)
144
144
- [Overview of deploying a highly available PostgreSQL database on Azure Kubernetes Service (AKS)](/azure/aks/postgresql-ha-overview#storage-considerations)
Copy file name to clipboardExpand all lines: articles/storage/container-storage/use-container-storage-with-local-disk.md
+10-6Lines changed: 10 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ ms.custom: references_regions
19
19
20
20
## What is local NVMe?
21
21
22
-
When your application needs sub-millisecond storage latency and high throughput, you can use local NVMe with Azure Container Storage to meet your performance requirements. Ephemeral means that the disks are deployed on the local virtual machine (VM) hosting the AKS cluster and not saved to an Azure storage service. Data is lost on these disks if you stop/deallocate your VM. Local NVMe disks are offered on select Azure VM families such as [storage-optimized](/azure/virtual-machines/sizes/overview#storage-optimized) VMs.
22
+
When your application needs sub-millisecond storage latency and high throughput, you can use local NVMe disks with Azure Container Storage to meet your performance requirements. Ephemeral means that the disks are deployed on the local virtual machine (VM) hosting the AKS cluster and not saved to an Azure storage service. Data is lost on these disks if you stop/deallocate your VM. Local NVMe disks are offered on select Azure VM families such as [storage-optimized](/azure/virtual-machines/sizes/overview#storage-optimized) VMs.
23
23
24
24
By default, Azure Container Storage creates *generic ephemeral volumes* when using local NVMe disks. For use cases that require *persistent volume claims*, you can add the annotation `localdisk.csi.acstor.io/accept-ephemeral-storage: "true"` in your persistent volume claim template.
25
25
@@ -28,21 +28,20 @@ By default, Azure Container Storage creates *generic ephemeral volumes* when usi
28
28
To maximize performance, Azure Container Storage automatically stripes data across all available local NVMe disks on a per-VM basis. Striping is a technique where data is divided into small chunks and evenly written across multiple disks simultaneously, which increases throughput and improves overall I/O performance. This behavior is enabled by default and cannot be disabled.
29
29
30
30
Because performance aggregates across those striped devices, larger VM sizes that expose more NVMe drives can unlock substantially higher IOPS and bandwidth. Selecting a larger VM family lets your workloads benefit from the extra aggregate throughput without additional configuration.
31
-
32
31
For example, the [Lsv3 series](/azure/virtual-machines/sizes/storage-optimized/lsv3-series?tabs=sizestoragelocal) scales from a single 1.92-TB NVMe drive on Standard_L8s_v3 (around 400,000 IOPS and 2,000 MB/s) up to 10 NVMe drives on Standard_L80s_v3 (about 3.8 million IOPS and 20,000 MB/s).
33
32
34
33
## Prerequisites
35
34
36
35
- If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn) before you begin.
37
36
38
-
- This article requires the latest version (2.77.0 or later) of the Azure CLI. See [How to install the Azure CLI](/cli/azure/install-azure-cli). Don't use Azure Cloud Shell, because `az upgrade` isn't available in Cloud Shell. Be sure to run the commands in this article with administrative privileges.
37
+
- This article requires the latest version (2.77.0 or later) of the Azure CLI. See [How to install the Azure CLI](/cli/azure/install-azure-cli). Avoid Azure Cloud Shell, because `az upgrade` isn't available in Cloud Shell. Be sure to run the commands in this article with administrative privileges.
38
+
39
+
-[Review the installation instructions](install-container-storage-aks.md) and ensure Azure Container Storage is properly installed.
39
40
40
41
- You need the Kubernetes command-line client, `kubectl`. You can install it locally by running the `az aks install-cli` command.
41
42
42
43
- Check if your target region is supported in [Azure Container Storage regions](container-storage-introduction.md#regional-availability).
43
44
44
-
- You can now use clusters with a single node, though multi-node configurations are still recommended.
45
-
46
45
## Choose a VM type that supports local NVMe
47
46
48
47
Local NVMe disks are only available in certain types of VMs, for example, [storage-optimized VMs](/azure/virtual-machines/sizes/overview#storage-optimized) or [GPU accelerated VMs](/azure/virtual-machines/sizes/overview#gpu-accelerated). If you plan to use local NVMe capacity, choose one of these VM sizes.
@@ -68,9 +67,12 @@ nodepool1 standard_l8s_v3
68
67
69
68
Follow these steps to create and attach a generic ephemeral volume using Azure Container Storage.
70
69
70
+
> [!NOTE]
71
+
> If you haven't already done so, [install Azure Container Storage](install-container-storage-aks.md).
72
+
71
73
### 1. Create a storage class
72
74
73
-
Unlike previous versions that required creating a custom storage pool resource, Azure Container Storage (version 2.x.x) uses standard Kubernetes storage classes. This change simplifies the storage configuration process.
75
+
Unlike previous versions that required creating a custom storage pool resource, Azure Container Storage (version 2.x.x) uses standard Kubernetes storage classes.
74
76
75
77
Follow these steps to create a storage class using local NVMe.
76
78
@@ -303,5 +305,7 @@ kubectl delete storageclass local
303
305
## See also
304
306
305
307
-[What is Azure Container Storage?](container-storage-introduction.md)
308
+
-[Install Azure Container Storage with AKS](install-container-storage-aks.md)
306
309
-[Use Azure Container Storage (version 1.x.x) with local NVMe](use-container-storage-with-local-disk-version-1.md)
307
310
-[Overview of deploying a highly available PostgreSQL database on Azure Kubernetes Service (AKS)](/azure/aks/postgresql-ha-overview#storage-considerations)
311
+
-[Best practices for ephemeral NVMe data disks in Azure Kubernetes Service (AKS)](/azure/aks/best-practices-storage-nvme)
0 commit comments