From 67a4da4e1ab40feade3144f3cdcf48a35f46d2f8 Mon Sep 17 00:00:00 2001 From: Bob Furu Date: Wed, 22 Apr 2020 19:11:53 -0400 Subject: [PATCH] BZ1782389 - Fix xref for vsphere install --- storage/persistent_storage/persistent-storage-vsphere.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/storage/persistent_storage/persistent-storage-vsphere.adoc b/storage/persistent_storage/persistent-storage-vsphere.adoc index 9463b2014c..fd02f46fc8 100644 --- a/storage/persistent_storage/persistent-storage-vsphere.adoc +++ b/storage/persistent_storage/persistent-storage-vsphere.adoc @@ -27,7 +27,7 @@ requested by users. Dynamically provisioning VMware vSphere volumes is the recommended method. .Prerequisites -An {product-title} cluster installed on a VMware vSphere version that meets the requirements for the components that you use. See xref:../../installing/installing_vsphere/installing-vsphere.adoc[Installing a cluster on vSphere] +* An {product-title} cluster installed on a VMware vSphere version that meets the requirements for the components that you use. See xref:../../installing/installing_vsphere/installing-vsphere.adoc[Installing a cluster on vSphere] for information about vSphere version support. You can use either of the following procedures to dynamically provision these volumes using the default StorageClass.