Skip to content

Commit d6414f5

Browse files
fhryo-msftkhdownie
andauthored
Update articles/storage/container-storage/manage-local-container-storage-interface-driver-placement.md
Co-authored-by: Ken Downie <[email protected]>
1 parent e6a7bc1 commit d6414f5

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/storage/container-storage/manage-local-container-storage-interface-driver-placement.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.custom: references_regions
1414

1515
In Kubernetes clusters, CSI drivers are typically deployed as DaemonSets, running on all nodes by default. However, in production environments, certain nodes may be equipped with specialized hardware (such as local NVMe disks), specific instance types, or designated roles that make them more suitable for particular storage workloads.
1616

17-
Azure Container Storage uses local CSI driver to manage local NVMe volumes. By configuring node affinity in local NVMe storage class, you can control the placement of Local CSI drivers to ensure they run only on nodes that meet the designed conditions. This approach helps optimize resource utilization and minimizes the impact on other nodes in the cluster.
17+
Azure Container Storage uses the local CSI driver to manage local NVMe volumes. By configuring node affinity in the local NVMe storage class, you can control the placement of local CSI drivers to ensure they run only on nodes that meet the designed conditions. This approach helps optimize resource utilization and minimizes the impact on other nodes in the cluster.
1818

1919
## When to consider managing local CSI driver placement
2020

0 commit comments

Comments
 (0)