Skip to content

Commit ae93851

Browse files
Merge pull request #269847 from khdownie/kendownie032124-2
update quickstart
2 parents 535642b + b8e9f80 commit ae93851

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/storage/container-storage/container-storage-aks-quickstart.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Create a Linux-based Azure Kubernetes Service (AKS) cluster, instal
44
author: khdownie
55
ms.service: azure-container-storage
66
ms.topic: quickstart
7-
ms.date: 03/19/2024
7+
ms.date: 03/21/2024
88
ms.author: kendownie
99
ms.custom:
1010
- devx-track-azurecli
@@ -21,7 +21,7 @@ ms.custom:
2121

2222
## Getting started
2323

24-
- Take note of your Azure subscription ID. We recommend using a subscription on which you have a [Kubernetes contributor](../../role-based-access-control/built-in-roles.md#kubernetes-extension-contributor) role if you want to use Azure Disks or Ephemeral Disk as data storage. If you want to use Azure Elastic SAN as data storage, you'll need an [Owner](../../role-based-access-control/built-in-roles.md#owner) role on the Azure subscription.
24+
- Take note of your Azure subscription ID. If you want to use Azure Elastic SAN as data storage, you'll need an [Azure role-based access control (Azure RBAC) Owner](../../role-based-access-control/built-in-roles.md#owner) role on the Azure subscription. Owner-level access grants the Azure Container Storage extension the proper permissions to interact with Elastic SAN's API. If you're planning on using Azure Disks or Ephemeral Disk as data storage, you don't need special permissions on your subscription.
2525

2626
- [Launch Azure Cloud Shell](https://shell.azure.com), or if you're using a local installation, sign in to Azure by using the [az login](/cli/azure/reference-index#az-login) command.
2727

@@ -84,7 +84,7 @@ Before deploying Azure Container Storage, you'll need to decide which back-end s
8484
- **Ephemeral Disk**: This option uses local NVMe drives or temp SSD on the AKS cluster nodes. It's extremely latency sensitive (low sub-ms latency), so it's best for applications with no data durability requirement or with built-in data replication support such as Cassandra. AKS discovers the available ephemeral storage on AKS nodes and acquires the drives for volume deployment.
8585

8686
> [!NOTE]
87-
> For Azure Elastic SAN and Azure Disks, Azure Container Storage will deploy the backing storage for you as part of the installation, as long as you have owner-level access to the Azure subscription. You don't need to create your own Elastic SAN or Azure Disk.
87+
> For Azure Elastic SAN and Azure Disks, Azure Container Storage will deploy the backing storage for you as part of the installation. You don't need to create your own Elastic SAN or Azure Disk. In order to use Elastic SAN, you'll need an [Azure role-based access control (Azure RBAC) Owner](../../role-based-access-control/built-in-roles.md#owner) role on the Azure subscription.
8888
8989
### Resource consumption
9090

0 commit comments

Comments
 (0)