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
index a369fdb31112..4e2dc48e5561 100644
--- a/installing/installing_vsphere/ipi/installing-restricted-networks-installer-provisioned-vsphere.adoc
+++ b/installing/installing_vsphere/ipi/installing-restricted-networks-installer-provisioned-vsphere.adoc
@@ -52,8 +52,6 @@ include::modules/installation-vsphere-regions-zones-host-groups.adoc[leveloffset
 
 * xref:../../../storage/container_storage_interface/persistent-storage-csi-vsphere.adoc#persistent-storage-csi-vsphere-top-aware_persistent-storage-csi-vsphere[VMware vSphere CSI Driver Operator]
 
-* xref:../../../nodes/clusters/nodes-cluster-enabling-features.adoc#nodes-cluster-enabling[Enabling features using feature gates]
-
 include::modules/installation-initializing.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
@@ -68,10 +66,6 @@ include::modules/configuring-vsphere-regions-zones.adoc[leveloffset=+2]
 
 include::modules/configuring-vsphere-host-groups.adoc[leveloffset=+2]
 
-[role="_additional-resources"]
-.Additional resources
-* xref:../../../nodes/clusters/nodes-cluster-enabling-features.adoc#nodes-cluster-enabling[Enabling features using feature gates]
-
 // Services for a user-managed load balancer
 include::modules/nw-osp-services-external-load-balancer.adoc[leveloffset=+1]
 
diff --git a/installing/installing_vsphere/ipi/installing-vsphere-installer-provisioned-customizations.adoc b/installing/installing_vsphere/ipi/installing-vsphere-installer-provisioned-customizations.adoc
index 22a8157486eb..c008e795616a 100644
--- a/installing/installing_vsphere/ipi/installing-vsphere-installer-provisioned-customizations.adoc
+++ b/installing/installing_vsphere/ipi/installing-vsphere-installer-provisioned-customizations.adoc
@@ -48,8 +48,6 @@ include::modules/installation-vsphere-regions-zones-host-groups.adoc[leveloffset
 
 * xref:../../../storage/container_storage_interface/persistent-storage-csi-vsphere.adoc#persistent-storage-csi-vsphere-top-aware_persistent-storage-csi-vsphere[{vmw-full} CSI Driver Operator]
 
-* xref:../../../nodes/clusters/nodes-cluster-enabling-features.adoc#nodes-cluster-enabling[Enabling features using feature gates]
-
 include::modules/installation-initializing.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
@@ -66,10 +64,6 @@ include::modules/configuring-vsphere-regions-zones.adoc[leveloffset=+2]
 
 include::modules/configuring-vsphere-host-groups.adoc[leveloffset=+2]
 
-[role="_additional-resources"]
-.Additional resources
-* xref:../../../nodes/clusters/nodes-cluster-enabling-features.adoc#nodes-cluster-enabling[Enabling features using feature gates]
-
 // Specifying multiple NICS
 include::modules/installation-vsphere-multiple-nics.adoc[leveloffset=+2]
 
diff --git a/installing/installing_vsphere/post-install-vsphere-zones-regions-configuration.adoc b/installing/installing_vsphere/post-install-vsphere-zones-regions-configuration.adoc
index 0a38a216eb89..76dd3c665a57 100644
--- a/installing/installing_vsphere/post-install-vsphere-zones-regions-configuration.adoc
+++ b/installing/installing_vsphere/post-install-vsphere-zones-regions-configuration.adoc
@@ -51,8 +51,4 @@ include::modules/references-regions-zones-infrastructure-vsphere.adoc[leveloffse
 .Additional resources
 * xref:../../installing/installing_vsphere/post-install-vsphere-zones-regions-configuration.adoc#specifying-regions-zones-infrastructure-vsphere_post-install-vsphere-zones-regions-configuration[Specifying multiple regions and zones for your cluster on vSphere]
 
-include::modules/specifying-host-groups-vsphere.adoc[leveloffset=+1]
-
-[role="_additional-resources"]
-.Additional resources
-* xref:../../nodes/clusters/nodes-cluster-enabling-features.adoc#nodes-cluster-enabling[Enabling features using feature gates]
\ No newline at end of file
+include::modules/specifying-host-groups-vsphere.adoc[leveloffset=+1]
\ No newline at end of file
diff --git a/modules/configuring-vsphere-host-groups.adoc b/modules/configuring-vsphere-host-groups.adoc
index dcbd85e5658c..94373030d3ae 100644
--- a/modules/configuring-vsphere-host-groups.adoc
+++ b/modules/configuring-vsphere-host-groups.adoc
@@ -7,9 +7,6 @@
 [id="configuring-vsphere-host-groups_{context}"]
 = Configuring host groups for a VMware vCenter
 
-:FeatureName: OpenShift zones support for vSphere host groups
-include::snippets/technology-preview.adoc[]
-
 You can modify the default installation configuration file to deploy an {product-title} cluster on a {vmw-first} stretched cluster, where ESXi hosts are grouped into host groups by physical location.
 
 The default `install-config.yaml` file configuration from previous releases of {product-title} is deprecated. Though you can still use it, the {product-title} installer will display a warning message that indicates the use of deprecated fields in the configuration file.
@@ -20,7 +17,6 @@ The default `install-config.yaml` file configuration from previous releases of {
 * You have arranged your ESXi hosts into host groups.
 * You have granted the `Host.Inventory.EditCluster` privilege on the {vmw-short} vCenter cluster object.
 * You have downloaded and installed the `govc` command line tool. Instructions can be found on the VMware documentation website. Note that `govc` is an open-source tool that is not maintained by the Red{nbsp}Hat support team.
-* You have enabled the `TechPreviewNoUpgrade` feature set. For more information, see  "Enabling features using feature gates".
 +
 [IMPORTANT]
 ====
@@ -81,10 +77,6 @@ $ govc tags.attach -c <zone_tag_category> <zone_tag_for_host_group_1> /<datacent
 
 [source,yaml]
 ----
-featureSet: TechPreviewNoUpgrade
-featureGate:
-  - "VSphereHostVMGroupZonal=true"
-# ...
 platform:
   vsphere:
     vcenters:
diff --git a/modules/installation-configuration-parameters.adoc b/modules/installation-configuration-parameters.adoc
index a3262754a1c3..d0ccdf080e57 100644
--- a/modules/installation-configuration-parameters.adoc
+++ b/modules/installation-configuration-parameters.adoc
@@ -3297,30 +3297,14 @@ endif::vsphere[]
       region:
 |If you define multiple failure domains for your cluster, you must attach the tag to each vCenter data center. To define a region, use a tag from the `openshift-region` tag category. For a single vSphere data center environment, you do not need to attach a tag, but you must enter an alphanumeric value, such as `datacenter`, for the parameter.
 If you want to base your failure domains on host groups, attach these tags to your vSphere clusters instead of your data centers.
-
-[IMPORTANT]
-====
-OpenShift zones support for vSphere host groups is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
-
-For more information about the support scope of Red Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope].
-====
-
-*Value:* String
+|String
 
 |platform:
   vsphere:
     failureDomains:
       regionType:
 |Specifies the `ComputeCluster` region type to enable host groups.
-
-[IMPORTANT]
-====
-OpenShift zones support for vSphere host groups is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
-
-For more information about the support scope of Red Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope].
-====
-
-*Value:* String
+|String
 
 |platform:
   vsphere:
@@ -3336,30 +3320,14 @@ For more information about the support scope of Red Hat Technology Preview featu
       zone:
 |If you define multiple failure domains for your cluster, you must attach a tag to each vCenter cluster. To define a zone, use a tag from the `openshift-zone` tag category. For a single vSphere data center environment, you do not need to attach a tag, but you must enter an alphanumeric value, such as `cluster`, for the parameter.
 If you want to base your failure domains on host groups, define zones that correspond to your host groups instead of your clusters. Use these tags to associate each ESXi host with its host group.
-
-[IMPORTANT]
-====
-OpenShift zones support for vSphere host groups is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
-
-For more information about the support scope of Red Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope].
-====
-
-*Value:* String
+|String
 
 |platform:
   vsphere:
     failureDomains:
       zoneType:
 |Specifies the `HostGroup` zone type to enable host groups.
-
-[IMPORTANT]
-====
-OpenShift zones support for vSphere host groups is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
-
-For more information about the support scope of Red Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope].
-====
-
-*Value:* String
+|String
 
 |platform:
   vsphere:
@@ -3427,15 +3395,7 @@ endif::vsphere[]
       topology:
         hostGroup:
 |Specifies the vSphere host group to associate with the failure domain.
-
-[IMPORTANT]
-====
-OpenShift zones support for vSphere host groups is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
-
-For more information about the support scope of Red Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope].
-====
-
-*Value:* String
+|String
 
 |platform:
   vsphere:
diff --git a/modules/installation-vsphere-regions-zones-host-groups.adoc b/modules/installation-vsphere-regions-zones-host-groups.adoc
index 605d56354536..aba48e428e18 100644
--- a/modules/installation-vsphere-regions-zones-host-groups.adoc
+++ b/modules/installation-vsphere-regions-zones-host-groups.adoc
@@ -7,9 +7,6 @@
 [id="installation-vsphere-regions-zones-host-groups_{context}"]
 = VMware vSphere host group enablement
 
-:FeatureName: OpenShift zones support for vSphere host groups
-include::snippets/technology-preview.adoc[]
-
 When deploying an {product-title} cluster to {vmw-first}, you can map your {vmw-short} host groups onto {product-title} failure domains. This is useful if you are using a stretched cluster configuration, where ESXi hosts are grouped into host groups by physical location.
 
 To enable this feature, you must meet the following requirements:
@@ -19,19 +16,6 @@ To enable this feature, you must meet the following requirements:
 * You must create a vCenter tag in the `openshift-zone` tag category for each host group and then attach the correct tag to each ESXi host.
 * You must define multiple failure domains for your {product-title} cluster in the `install-config.yaml` file.
 * You must grant the `Host.Inventory.EditCluster` privilege on the {vmw-short} vCenter cluster object.
-* You must include the following parameters in your `install-config.yaml` file to enable this Technology Preview feature:
-+
-[source,yaml]
-----
-featureSet: TechPreviewNoUpgrade
-featureGate:
-  - "VSphereHostVMGroupZonal=true"
-----
-+
-[NOTE]
-====
-For further information on feature gates, see "Enabling features using feature gates".
-====
 
 Review the following key terms, which correspond to parameters in your `install-config.yaml` file that you must configure to enable this feature:
 
diff --git a/modules/specifying-host-groups-vsphere.adoc b/modules/specifying-host-groups-vsphere.adoc
index 3e1c2cc4ae23..f92dae2b6d25 100644
--- a/modules/specifying-host-groups-vsphere.adoc
+++ b/modules/specifying-host-groups-vsphere.adoc
@@ -7,9 +7,6 @@
 
 You can configure the `infrastructures.config.openshift.io` configuration resource to specify multiple host groups for your {product-title} cluster that runs on a {vmw-first} instance. This is necessary if your {vmw-short} instance is in a stretched cluster configuration, with your ESXi hosts and storage distributed across multiple physical data centers. Use this procedure if you did not already configure host groups for your {product-title} cluster at installation, or if you need to update your {product-title} cluster with additional host groups. 
 
-:FeatureName: OpenShift zones support for vSphere host groups
-include::snippets/technology-preview.adoc[]
-
 .Prerequisites
 
 * ESXi hosts are grouped into host groups, which are linked via VM-host affinity rules to corresponding virtual machine (VM) groups. See the following example `govc` commands for details:
@@ -27,18 +24,17 @@ govc cluster.group.create -name <vm_group_1> -vm
 govc cluster.group.create -name <vm_group_2> -vm
 
 # Create VM-host affinity rules:
-govc cluster.rule.create -name <rule_1> -enable -vm-host -vm-group <vm_group_1> -host-affine-group <host_group_1> 
-govc cluster.rule.create -name <rule_2> -enable -vm-host -vm-group <vm_group_2> -host-affine-group <host_group_2> 
+govc cluster.rule.create -name <rule_1> -enable -vm-host -vm-group <vm_group_1> -host-affine-group <host_group_1>
+govc cluster.rule.create -name <rule_2> -enable -vm-host -vm-group <vm_group_2> -host-affine-group <host_group_2>
 
 # Add ESXi hosts to host groups:
-govc cluster.group.change -name <host_group_1> <esxi_host_1_ip> 
-govc cluster.group.change -name <host_group_2> <esxi_host_2_ip> 
+govc cluster.group.change -name <host_group_1> <esxi_host_1_ip>
+govc cluster.group.change -name <host_group_2> <esxi_host_2_ip>
 ----
 * `openshift-region` and `openshift-zone` tag categories are created on the vCenter server.
 * Compute clusters have tags from the `openshift-region` tag category.
-* ESXi hosts within host groups have tags from the `openshift-zone` tag category. 
+* ESXi hosts within host groups have tags from the `openshift-zone` tag category.
 * `Host.Inventory.EditCluster` privilege is granted on the {vmw-short} vCenter cluster object.
-* `TechPreviewNoUpgrade` feature set is enabled. For more information, "see Enabling features using feature gates". 
 
 .Procedure
 
@@ -51,7 +47,7 @@ govc cluster.group.change -name <host_group_2> <esxi_host_2_ip>
 $ oc get infrastructures.config.openshift.io cluster -o yaml > <name_of_infrastructure_file>.yaml
 ----
 +
-.. Edit your infrastructure file to include a failure domain for each host group in your {vmw-short} cluster.  Refer to the following YAML file for an example of this configuration. Ensure you replace any values wrapped in angle brackets (`< >`) with your values:
+.. Edit your infrastructure file to include a failure domain for each host group in your {vmw-short} cluster. Refer to the following YAML file for an example of this configuration. Ensure you replace any values wrapped in angle brackets (`< >`) with your values:
 +
 [source,yaml]
 ----