Update docs/big-data-cluster/concept-data-persistence.md

chuckheinzelman · web-flow · commit f147d84094f0 · 2023-09-27T11:53:23.000-05:00
diff --git a/docs/big-data-cluster/concept-data-persistence.md b/docs/big-data-cluster/concept-data-persistence.md
@@ -16,7 +16,7 @@ ms.topic: conceptual
 
 [!INCLUDE[big-data-clusters-banner-retirement](../includes/bdc-banner-retirement.md)]
 
-[Persistent volumes](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) provide a plug-in model for storage in Kubernetes. In this model, the way that storage is provided is abstracted from how it's consumed. Therefore, you can bring your own highly available storage and plug it into the SQL Server big data cluster. While Kubernetes supports [various kinds of storage solutions](https://kubernetes.io/docs/concepts/storage/storage-classes/#provisioner), including Azure disks and files, Network File System (NFS), and local storage, Big Data Clusters are only supported on tested configurations. Please see our [platform release notes](https://learn.microsoft.com/sql/big-data-cluster/release-notes-big-data-cluster?view=sql-server-ver15&viewFallbackFrom=sql-server-ver16#tested-configurations) for the supported configurations.
+[Persistent volumes](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) provide a plug-in model for storage in Kubernetes. In this model, the way that storage is provided is abstracted from how it's consumed. Therefore, you can bring your own highly available storage and plug it into the SQL Server big data cluster. While Kubernetes supports [various kinds of storage solutions](https://kubernetes.io/docs/concepts/storage/storage-classes/#provisioner), including Azure disks and files, Network File System (NFS), and local storage, Big Data Clusters are only supported on tested configurations. Please see our [platform release notes](https://learn.microsoft.com/sql/big-data-cluster/release-notes-big-data-cluster?view=sql-server-ver15&preserve-view=true&viewFallbackFrom=sql-server-ver16#tested-configurations) for the supported configurations.
 
 > [!IMPORTANT]
 > If you are deploying the big data cluster in Azure using one of the managed Kubernetes services (AKS or ARO), keep in mind there are limitations that you might need to accomodate, depending on your application workload requirements. For example, volumes that use Azure managed disks are currently not zone-redundant resources. Volumes cannot be attached across zones and must be co-located in the same zone as a given node hosting the target pod. In this specific case, you might want to use additional high availability solutions that are available with SQL Server Big Data Clusters. See [here](/azure/aks/availability-zones) for more details on Azure Kubernetes service and availability zones.
