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-files-csi.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -268,11 +268,11 @@ Filesystem
268
268
269
269
## Use a persistent volume with private Azure Files storage (private endpoint)
270
270
271
-
If your Azure Files resources are protected with a private endpoint, you must create your own storage class that's customized with the following parameters:
271
+
If your Azure Files resources are protected with a private endpoint, you must create your own storage class. Make sure that you've [configured your DNS settings to resolve the private endpoint IP address to the FQDN of the connection string][azure-private-endpoint-dns]. that's customized with the following parameters:
272
272
273
273
*`resourceGroup`: The resource group where the storage account is deployed.
274
274
*`storageAccount`: The storage account name.
275
-
*`server`: The FQDN of the storage account's private endpoint (for example, `<storage account name>.privatelink.file.core.windows.net`).
275
+
*`server`: The FQDN of the storage account's private endpoint.
276
276
277
277
Create a file named `private-azure-file-sc.yaml`, and then paste the following example manifest in the file. Replace the values for `<resourceGroup>` and `<storageAccountName>`.
0 commit comments