OSDOCS-15960:moving from TP to GA

modules/installation-configuration-parameters.adoc

@@ -2785,7 +2785,6 @@ Additional {gcp-short} configuration parameters are described in the following t
 |Enables user-provisioned DNS instead of the default cluster-provisioned DNS solution. If you use this feature, you must provide your own DNS solution that includes records for `api.<cluster_name>.<base_domain>.` and `*.apps.<cluster_name>.<base_domain>.`.
 
 *Value:* `Enabled` or `Disabled`. The default value is `Disabled`.
-`userProvisionedDNS` is a Technology Preview feature.
 
 |platform:
   gcp:

modules/installation-gcp-managing-dns-solution.adoc

@@ -3,13 +3,13 @@
 [id="installation-gcp-enabling-user-managed-DNS_{context}"]
 = Enabling a user-managed DNS
 
-You can install a cluster with a domain name server (DNS) solution that you manage instead of the default cluster-provisioned DNS solution. As a result, you can manage the API and Ingress DNS records in your own system rather than adding the records to the DNS of the cloud. For example, your organization's security policies might not allow the use of public DNS services such as {gcp-full} DNS. In such scenarios, you can use your own DNS service to bypass the public DNS service and manage your own DNS for the IP addresses of the API and Ingress services.
+[role="_abstract"]
+You can install a cluster with a domain name server (DNS) solution that you manage instead of the default cluster-provisioned DNS solution. As a result, you can manage the API and Ingress DNS records in your own system rather than adding the records to the DNS of the cloud.
+
+For example, your organization's security policies might not allow the use of public DNS services such as {gcp-full} DNS. In such scenarios, you can use your own DNS service to bypass the public DNS service and manage your own DNS for the IP addresses of the API and Ingress services.
 
 If you enable user-managed DNS during installation, the installation program provisions DNS records for the API and Ingress services only within the cluster. To ensure access from outside the cluster, you must provision the DNS records in an external DNS service of your choice for the API and Ingress services after installation.
 
-:FeatureName: User-provisioned DNS
-include::snippets/technology-preview.adoc[leveloffset=+1]
-
 .Prerequisites
 
 * You installed the `jq` package.
@@ -20,16 +20,13 @@ include::snippets/technology-preview.adoc[leveloffset=+1]
 +
 [source,yaml]
 ----
-featureSet: CustomNoUpgrade
-featureGates: ["GCPClusterHostedDNS=true"]
-
-# ...
-
 platform:
   gcp:
-    userProvisionedDNS: Enabled <1>
+    userProvisionedDNS: Enabled
 ----
-<1> Enable DNS management.
++
+where:
 
+`Enabled`:: Enables user-provisioned DNS management.
 
 For information about provisioning your DNS records for the API server and the Ingress services, see "Provisioning your own DNS records".

modules/installation-gcp-provisioning-dns-records.adoc

@@ -3,13 +3,13 @@
 [id="installation-gcp-provisioning-own-dns-records_{context}"]
 = Provisioning your own DNS records
 
-Before you use this feature, you must add the `userProvisionedDNS` parameter to the `install-config.yaml` file and enable the parameter. For more information, see "Enabling a user-managed DNS".
-
+[role="_abstract"]
 Use the IP address of the API server to provision your own DNS record with the `api.<cluster_name>.<base_domain>.` hostname by using your cluster name and base cluster domain. Use the IP address of the Ingress service to provision your own DNS record with the `*.apps.<cluster_name>.<base_domain>.` hostname by using your cluster name and base cluster domain.
 
-
-:FeatureName: User-provisioned DNS
-include::snippets/technology-preview.adoc[leveloffset=+1]
+[IMPORTANT]
+====
+Before you use this feature, you must add the `userProvisionedDNS` parameter to the `install-config.yaml` file and enable the parameter. For more information, see "Enabling a user-managed DNS".
+====
 
 .Prerequisites