All single vcenter ref changes

Shubha Narayanan · Shubha Narayanan · commit adbabdbb06d7 · 2024-09-11T20:30:51.000+05:30
diff --git a/installing/installing_vmc/installing-restricted-networks-vmc-user-infra.adoc b/installing/installing_vmc/installing-restricted-networks-vmc-user-infra.adoc
@@ -10,7 +10,8 @@ In {product-title} version {product-version}, you can install a cluster on VMwar
 
 Once you configure your VMC environment for {product-title} deployment, you use the {product-title} installation program from the bastion management host, co-located in the VMC environment. The installation program and control plane automates the process of deploying and managing the resources needed for the {product-title} cluster.
 
-include::snippets/vcenter-support.adoc[]
+:FeatureName: Support for multiple vCenters
+include::snippets/technology-preview.adoc[]
 
 include::modules/setting-up-vmc-for-vsphere.adoc[leveloffset=+1]
 include::modules/vmc-sizer-tool.adoc[leveloffset=+2]
diff --git a/installing/installing_vmc/installing-vmc-network-customizations-user-infra.adoc b/installing/installing_vmc/installing-vmc-network-customizations-user-infra.adoc
@@ -12,7 +12,8 @@ Once you configure your VMC environment for {product-title} deployment, you use
 
 By customizing your network configuration, your cluster can coexist with existing IP address allocations in your environment and integrate with existing VXLAN configurations. You must set most of the network configuration parameters during installation, and you can modify only `kubeProxy` configuration parameters in a running cluster.
 
-include::snippets/vcenter-support.adoc[]
+:FeatureName: Support for multiple vCenters
+include::snippets/technology-preview.adoc[]
 
 include::modules/setting-up-vmc-for-vsphere.adoc[leveloffset=+1]
 include::modules/vmc-sizer-tool.adoc[leveloffset=+2]
diff --git a/installing/installing_vmc/installing-vmc-user-infra.adoc b/installing/installing_vmc/installing-vmc-user-infra.adoc
@@ -11,7 +11,8 @@ In {product-title} version {product-version}, you can install a cluster on VMwar
 
 Once you configure your VMC environment for {product-title} deployment, you use the {product-title} installation program from the bastion management host, co-located in the VMC environment. The installation program and control plane automates the process of deploying and managing the resources needed for the {product-title} cluster.
 
-include::snippets/vcenter-support.adoc[]
+:FeatureName: Support for multiple vCenters
+include::snippets/technology-preview.adoc[]
 
 include::modules/setting-up-vmc-for-vsphere.adoc[leveloffset=+1]
 include::modules/vmc-sizer-tool.adoc[leveloffset=+2]
diff --git a/installing/installing_vsphere/ipi/installing-restricted-networks-installer-provisioned-vsphere.adoc b/installing/installing_vsphere/ipi/installing-restricted-networks-installer-provisioned-vsphere.adoc
@@ -8,7 +8,8 @@ toc::[]
 
 In {product-title} {product-version}, you can install a cluster on VMware vSphere infrastructure in a restricted network by creating an internal mirror of the installation release content.
 
-include::snippets/vcenter-support.adoc[]
+:FeatureName: Support for multiple vCenters
+include::snippets/technology-preview.adoc[]
 
 [id="prerequisites_installing-restricted-networks-installer-provisioned-vsphere"]
 == Prerequisites
diff --git a/installing/installing_vsphere/ipi/installing-vsphere-installer-provisioned-customizations.adoc b/installing/installing_vsphere/ipi/installing-vsphere-installer-provisioned-customizations.adoc
@@ -10,7 +10,8 @@ toc::[]
 In {product-title} version {product-version}, you can install a cluster on your
 VMware vSphere instance by using installer-provisioned infrastructure. To customize the installation, you modify parameters in the `install-config.yaml` file before you install the cluster.
 
-include::snippets/vcenter-support.adoc[]
+:FeatureName: Support for multiple vCenters
+include::snippets/technology-preview.adoc[]
 
 [id="prerequisites_installing-vsphere-installer-provisioned-customizations"]
 == Prerequisites
diff --git a/installing/installing_vsphere/ipi/installing-vsphere-installer-provisioned-network-customizations.adoc b/installing/installing_vsphere/ipi/installing-vsphere-installer-provisioned-network-customizations.adoc
@@ -11,7 +11,8 @@ VMware vSphere instance by using installer-provisioned infrastructure with custo
 
 You must set most of the network configuration parameters during installation, and you can modify only `kubeProxy` configuration parameters in a running cluster.
 
-include::snippets/vcenter-support.adoc[]
+:FeatureName: Support for multiple vCenters
+include::snippets/technology-preview.adoc[]
 
 [id="prerequisites_installing-vsphere-installer-provisioned-network-customizations"]
 == Prerequisites
diff --git a/installing/installing_vsphere/ipi/installing-vsphere-installer-provisioned.adoc b/installing/installing_vsphere/ipi/installing-vsphere-installer-provisioned.adoc
@@ -9,7 +9,8 @@ toc::[]
 In {product-title} version {product-version}, you can install a cluster on your
 VMware vSphere instance by using installer-provisioned infrastructure.
 
-include::snippets/vcenter-support.adoc[]
+:FeatureName: Support for multiple vCenters
+include::snippets/technology-preview.adoc[]
 
 [id="prerequisites_installing-vsphere-installer-provisioned_{context}"]
 == Prerequisites
diff --git a/installing/installing_vsphere/upi/installing-restricted-networks-vsphere.adoc b/installing/installing_vsphere/upi/installing-restricted-networks-vsphere.adoc
@@ -9,7 +9,8 @@ toc::[]
 In {product-title} version {product-version}, you can install a cluster on
 VMware vSphere infrastructure that you provision in a restricted network.
 
-include::snippets/vcenter-support.adoc[]
+:FeatureName: Support for multiple vCenters
+include::snippets/technology-preview.adoc[]
 
 [IMPORTANT]
 ====
diff --git a/installing/installing_vsphere/upi/installing-vsphere-network-customizations.adoc b/installing/installing_vsphere/upi/installing-vsphere-network-customizations.adoc
@@ -12,7 +12,8 @@ configuration options. By customizing your network configuration, your cluster
 can coexist with existing IP address allocations in your environment and
 integrate with existing MTU and VXLAN configurations.
 
-include::snippets/vcenter-support.adoc[]
+:FeatureName: Support for multiple vCenters
+include::snippets/technology-preview.adoc[]
 
 You must set most of the network configuration parameters during installation,
 and you can modify only `kubeProxy` configuration parameters in a running
diff --git a/installing/installing_vsphere/upi/installing-vsphere.adoc b/installing/installing_vsphere/upi/installing-vsphere.adoc
@@ -10,7 +10,8 @@ toc::[]
 In {product-title} version {product-version}, you can install a cluster on
 VMware vSphere infrastructure that you provision.
 
-include::snippets/vcenter-support.adoc[]
+:FeatureName: Support for multiple vCenters
+include::snippets/technology-preview.adoc[]
 
 [IMPORTANT]
 ====
diff --git a/modules/configuring-vsphere-regions-zones.adoc b/modules/configuring-vsphere-regions-zones.adoc
@@ -10,7 +10,7 @@
 :_mod-docs-content-type: PROCEDURE
 [id="configuring-vsphere-regions-zones_{context}"]
 = Configuring regions and zones for a VMware vCenter
-You can modify the default installation configuration file, so that you can deploy an {product-title} cluster to multiple vSphere data centers that run in a single VMware vCenter.
+You can modify the default installation configuration file, so that you can deploy an {product-title} cluster to multiple vSphere data centers.
 
 The default `install-config.yaml` file configuration from the previous release of {product-title} is deprecated. You can continue to use the deprecated default configuration, but the `openshift-installer` will prompt you with a warning message that indicates the use of deprecated fields in the configuration file.
 
diff --git a/modules/installation-configuration-parameters.adoc b/modules/installation-configuration-parameters.adoc
@@ -2807,7 +2807,7 @@ endif::vsphere[]
 |platform:
   vsphere:
     vcenters:
-|Configures the connection details so that services can communicate with a vCenter server. Currently, only a single vCenter server is supported.
+|Configures the connection details so that services can communicate with a vCenter server.
 |An array of vCenter configuration objects.
 
 |platform:
diff --git a/modules/installation-initializing.adoc b/modules/installation-initializing.adoc
@@ -333,7 +333,7 @@ The installation program connects to your vCenter instance.
 +
 [NOTE]
 ====
-After you create the installation configuration file, you can modify the file to create a multiple vSphere data center environment. This means that you can deploy an {product-title} cluster to multiple vSphere data centers that run in a single VMware vCenter. For more information about creating this environment, see the section named _VMware vSphere region and zone enablement_.
+After you create the installation configuration file, you can modify the file to create a multiple vSphere data center environment. This means that you can deploy an {product-title} cluster to multiple vSphere data centers. For more information about creating this environment, see the section named _VMware vSphere region and zone enablement_.
 ====
 
 ... Select the default vCenter datastore to use.
diff --git a/modules/installation-vsphere-regions-zones.adoc b/modules/installation-vsphere-regions-zones.adoc
@@ -11,7 +11,7 @@
 [id="installation-vsphere-regions-zones_{context}"]
 = VMware vSphere region and zone enablement
 
-You can deploy an {product-title} cluster to multiple vSphere data centers that run in a single VMware vCenter. Each data center can run multiple clusters. This configuration reduces the risk of a hardware failure or network outage that can cause your cluster to fail. To enable regions and zones, you must define multiple failure domains for your {product-title} cluster.
+You can deploy an {product-title} cluster to multiple vSphere data centers. Each data center can run multiple clusters. This configuration reduces the risk of a hardware failure or network outage that can cause your cluster to fail. To enable regions and zones, you must define multiple failure domains for your {product-title} cluster.
 
 [IMPORTANT]
 ====
diff --git a/modules/references-regions-zones-infrastructure-vsphere.adoc b/modules/references-regions-zones-infrastructure-vsphere.adoc
@@ -13,7 +13,7 @@ The following table lists mandatory parameters for defining multiple regions and
 |===
 |Parameter | Description
 
-|`vcenters` | The vCenter server for your {product-title} cluster. You can only specify one vCenter for your cluster.
+|`vcenters` | The vCenter servers for your {product-title} cluster. You can specify either a single vCenter, or up to 3 vCenters, which is currently a Technology Preview feature.
 |`datacenters` | vCenter data centers where VMs associated with the {product-title} cluster will be created or presently exist.
 |`port` | The TCP port of the vCenter server.
 |`server` | The fully qualified domain name (FQDN) of the vCenter server.
