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/aks/azure-blob-csi.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ The Azure Blob storage Container Storage Interface (CSI) driver is a [CSI specif
12
12
13
13
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.
14
14
15
-
Mounting Azure Blob storage as a file system into a container or pod, enables you to use blob storage with a number of applications that work massive amounts of unstructured data. For example:
15
+
When you mount Azure Blob storage as a file system into a container or pod, it enables you to use blob storage with a number of applications that work massive amounts of unstructured data. For example:
16
16
17
17
* Log file data
18
18
* Images, documents, and streaming video or audio
@@ -53,7 +53,7 @@ To enable the driver on an existing cluster, include the `--enable-blob-driver`
53
53
az aks update --enable-blob-driver -n myAKSCluster -g myResourceGroup
54
54
```
55
55
56
-
You're prompted to confirm there isn't an open-source Blob CSI driver installed. After confirming, it may take several minutes to complete this action. Once it's complete, you should see in the output the status of enabling the driver on your cluster. The following example is resembles the section indicating the results of the previous command:
56
+
You're prompted to confirm there isn't an open-source Blob CSI driver installed. After you confirm, it may take several minutes to complete this action. Once it's complete, you should see in the output the status of enabling the driver on your cluster. The following example resembles the section indicating the results of the previous command:
Copy file name to clipboardExpand all lines: articles/aks/azure-csi-blob-storage-provision.md
+9-4Lines changed: 9 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,7 @@ This section provides guidance for cluster administrators who want to provision
49
49
|storeAccountKey | Specify store account key to Kubernetes secret. <br><br> Note: <br> `false` means driver uses kubelet identity to get account key. |`true`,`false`| No |`true`|
50
50
|secretName | Specify secret name to store account key. || No |
51
51
|secretNamespace | Specify the namespace of secret to store account key. |`default`,`kube-system`, etc. | No | pvc namespace |
52
-
|isHnsEnabled | Enable `Hierarchical namespace` for Azure DataLake storage account. |`true`,`false`| No |`false`|
52
+
|isHnsEnabled | Enable `Hierarchical namespace` for Azure Data Lake storage account. |`true`,`false`| No |`false`|
53
53
|--- |**Following parameters are only for NFS protocol**| --- | --- |--- |
54
54
|mountPermissions | Specify mounted folder permissions. |The default is `0777`. If set to `0`, driver won't perform `chmod` after mount. |`0777`| No |
55
55
@@ -185,7 +185,7 @@ In this example, the following manifest configures mounting a Blob storage conta
185
185
186
186
#### Storage class using blobfuse
187
187
188
-
In this example, the following manifest configures using blobfuse and mount a Blob storage container. Use it to update the *skuName* parameter.
188
+
In this example, the following manifest configures using blobfuse and mounts a Blob storage container. Use it to update the *skuName* parameter.
189
189
190
190
1. Create a file named `blobfuse-sc.yaml`, and paste the following example manifest:
191
191
@@ -241,7 +241,7 @@ This section provides guidance for cluster administrators who want to create one
241
241
|volumeAttributes.secretName | Secret name that stores storage account name and key (only applies for SMB).| | No ||
242
242
|volumeAttributes.secretNamespace | Specify namespace of secret to store account key. | `default` | No | Pvc namespace|
243
243
|nodeStageSecretRef.name | Specify secret name that stores one of the following:<br> `azurestorageaccountkey`<br>`azurestorageaccountsastoken`<br>`msisecret`<br>`azurestoragespnclientsecret`. | |Existing Kubernetes secret name | No |
244
-
|nodeStageSecretRef.namespace | Specify the namespace of secret. | k8s namespace | Yes ||
244
+
|nodeStageSecretRef.namespace | Specify the namespace of secret. | Kubernetes namespace | Yes ||
245
245
|--- | **Following parameters are only for NFS protocol** | --- | --- | --- |
|--- | **Following parameters are only for NFS VNet setting** | --- | --- | --- |
@@ -438,6 +438,8 @@ Kubernetes needs credentials to access the Blob storage container created earlie
438
438
kubectl create -f pvc-blobfuse.yaml
439
439
```
440
440
441
+
---
442
+
441
443
### Use the persistence volume
442
444
443
445
The following YAML creates a pod that uses the persistent volume or persistent volume claim named **pvc-blob** created earlier, to mount the Azure Blob storage at the `/mnt/blob' path.
@@ -494,10 +496,13 @@ The following YAML creates a pod that uses the persistent volume or persistent v
Copy file name to clipboardExpand all lines: articles/aks/azure-csi-files-storage-provision.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
@@ -33,10 +33,10 @@ This section provides guidance for cluster administrators who want to provision
33
33
|--- | --- | --- | --- | ---
34
34
|skuName | Azure Files storage account type (alias: `storageAccountType`)|`Standard_LRS`, `Standard_ZRS`, `Standard_GRS`, `Standard_RAGRS`, `Standard_RAGZRS`,`Premium_LRS`, `Premium_ZRS`| No |`StandardSSD_LRS`<br> Minimum file share size for Premium account type is 100 GB.<br> ZRS account type is supported in limited regions.<br> NFS file share only supports Premium account type.|
35
35
|fsType | File System Type |`ext4`, `ext3`, `ext2`, `xfs`| Yes |`ext4` for Linux|
36
-
|location | Specify Azure region where Azure storage account will be created. |`eastus`, `westus`, etc. | No | If empty, driver uses the same location name as current AKS cluster.|
36
+
|location | Specify Azure region where Azure storage account will be created. |For example, `eastus`. | No | If empty, driver uses the same location name as current AKS cluster.|
37
37
|resourceGroup | Specify the resource group where the Azure Disks will be created | Existing resource group name | No | If empty, driver uses the same resource group name as current AKS cluster.|
38
38
|shareName | Specify Azure file share name | Existing or new Azure file share name. | No | If empty, driver generates an Azure file share name. |
39
-
|shareNamePrefix | Specify Azure file share name prefix created by driver. | Share name can only contain lowercase letters, numbers, hyphens, and length should be less than 21 characters. | No |
39
+
|shareNamePrefix | Specify Azure file share name prefix created by driver. | Share name can only contain lowercase letters, numbers, hyphens, and length should be fewer than 21 characters. | No |
40
40
|folderName | Specify folder name in Azure file share. | Existing folder name in Azure file share. | No | If folder name does not exist in file share, mount will fail. |
41
41
|shareAccessTier |[Access tier for file share][storage-tiers]| General purpose v2 account can choose between `TransactionOptimized` (default), `Hot`, and `Cool`. Premium storage account type for file shares only. | No | Empty. Use default setting for different storage account types.|
42
42
|accountAccessTier |[Access tier for storage account][access-tiers-overview]| Standard account can choose `Hot` or `Cool`, and Premium account can only choose `Premium`. | No | Empty. Use default setting for different storage account types. |
@@ -45,11 +45,11 @@ This section provides guidance for cluster administrators who want to provision
45
45
|allowBlobPublicAccess | Allow or disallow public access to all blobs or containers for storage account created by driver. |`true` or `false`| No |`false`|
46
46
|requireInfraEncryption | Specify whether or not the service applies a secondary layer of encryption with platform managed keys for data at rest for storage account created by driver. |`true` or `false`| No |`false`|
47
47
|storageEndpointSuffix | Specify Azure storage endpoint suffix. |`core.windows.net`, `core.chinacloudapi.cn`, etc. | No | If empty, driver uses default storage endpoint suffix according to cloud environment. For example, `core.windows.net`. |
48
-
|tags |[tags][tag-resources] are created in newly created storage account. | Tag format: 'foo=aaa,bar=bbb' | No | "" |
48
+
|tags |[tags][tag-resources] are created in new storage account. | Tag format: 'foo=aaa,bar=bbb' | No | "" |
49
49
|matchTags | Match tags when driver tries to find a suitable storage account. |`true` or `false`| No |`false`|
50
50
|--- |**Following parameters are only for SMB protocol**| --- | --- |
51
51
|subscriptionID | Specify Azure subscription ID where Azure file share is created. | Azure subscription ID | No | If not empty, `resourceGroup` must be provided. |
52
-
|storeAccountKey | Specify whether to store account key to k8s secret. |`true` or `false`<br>`false` means driver leverages kubelet identity to get account key. | No |`true`|
52
+
|storeAccountKey | Specify whether to store account key to Kubernetes secret. |`true` or `false`<br>`false` means driver leverages kubelet identity to get account key. | No |`true`|
53
53
|secretName | Specify secret name to store account key. || No |
54
54
|secretNamespace | Specify the namespace of secret to store account key. <br><br> **Note:** <br> If `secretNamespace` isn't specified, the secret is created in the same namespace as the pod. |`default`,`kube-system`, etc | No | Pvc namespace, for example `csi.storage.k8s.io/pvc/namespace`|
55
55
|useDataPlaneAPI | Specify whether to use [data plane API][data-plane-api] for file share create/delete/resize. This could solve the SRP API throttling issue because the data plane API has almost no limit, while it would fail when there is firewall or Vnet setting on storage account. |`true` or `false`| No |`false`|
@@ -248,7 +248,7 @@ This section provides guidance for cluster administrators who want to create one
248
248
|volumeAttributes.secretName | Specify a secret name that stores storage account name and key. | | No |
249
249
|volumeAttributes.secretNamespace | Specify a secret namespace. | `default`,`kube-system`, etc. | No | PVC namespace (`csi.storage.k8s.io/pvc/namespace`) |
250
250
|nodeStageSecretRef.name | Specify a secret name that stores storage account name and key. | Existing secret name | Yes ||
|--- | **Following parameters are only for NFS protocol** | --- | --- | --- |
253
253
|volumeAttributes.fsGroupChangePolicy | Indicates how a volumes ownership is changed by the driver. Pod `securityContext.fsGroupChangePolicy` is ignored. | `OnRootMismatch` (default), `Always`, `None` | No | `OnRootMismatch` |
254
254
|volumeAttributes.mountPermissions | Specify mounted folder permissions. The default is `0777` | | No ||
@@ -474,6 +474,7 @@ For associated best practices, see [Best practices for storage and backups in AK
0 commit comments