Skip to content

Commit bb53a97

Browse files
Merge pull request #248027 from andyzhangx/andyzhangx-patch-1
Update azure-csi-blob-storage-provision.md
2 parents cf005c8 + e1debf4 commit bb53a97

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/aks/azure-csi-blob-storage-provision.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ titleSuffix: Azure Kubernetes Service
44
description: Learn how to create a static or dynamic persistent volume with Azure Blob storage for use with multiple concurrent pods in Azure Kubernetes Service (AKS)
55
ms.topic: article
66
ms.custom: devx-track-linux
7-
ms.date: 08/15/2023
7+
ms.date: 08/16/2023
88
---
99

1010
# Create and use a volume with Azure Blob storage in Azure Kubernetes Service (AKS)
@@ -272,7 +272,7 @@ This section provides guidance for cluster administrators who want to create one
272272

273273
### Create a Blob storage container
274274

275-
When you create an Azure Blob storage resource for use with AKS, you can create the resource in the node resource group. This approach allows the AKS cluster to access and manage the blob storage resource. If instead you create the blob storage resource in a separate resource group, you must grant the Azure Kubernetes Service managed identity for your cluster the [Contributor][rbac-contributor-role] role to the blob storage resource group.
275+
When you create an Azure Blob storage resource for use with AKS, you can create the resource in the node resource group. This approach allows the AKS cluster to access and manage the blob storage resource.
276276

277277
For this article, create the container in the node resource group. First, get the resource group name with the [az aks show][az-aks-show] command and add the `--query nodeResourceGroup` query parameter. The following example gets the node resource group for the AKS cluster named **myAKSCluster** in the resource group named **myResourceGroup**:
278278

0 commit comments

Comments
 (0)