1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 03:47:04 +01:00

OSDOCS-15912: add note about enabling user-managed DNS for GCP installations

This commit is contained in:
Jesse Dohmann
2026-01-20 16:57:12 -08:00
committed by openshift-cherrypick-robot
parent 1cb9db44f4
commit 0d718857d1
2 changed files with 10 additions and 0 deletions

View File

@@ -190,6 +190,11 @@ status:
dnsZone:
id: ...
----
+
[NOTE]
====
For {gcp-first} installations, you can use a custom DNS solution. You must manually create a DNS record for any Gateways in Gateway API. For more information, see "Enabling a user-managed DNS" and "Provisioning your own DNS records".
====
. Create an `HTTPRoute` resource that directs requests to your already-created namespace and application called `example-app/example-app`:
+

View File

@@ -22,6 +22,11 @@ The following list details key aspects for a managed DNS management policy:
The following list details key aspects for a unmanaged DNS management policy:
* The Unmanaged DNS management policy for Ingress Controllers ensures that the lifecycle of the wildcard DNS record on the cloud provider is not automatically managed; instead, it becomes the responsibility of the cluster administrator.
+
[NOTE]
====
For {gcp-first} installations, you can use a custom DNS solution. Refer to the `DNSRecord` CR for information on what you need to include in the DNS record. For more information, see xref:../../../installing/installing_gcp/installing-gcp-customizations.adoc#installation-gcp-enabling-user-managed-DNS_installing-gcp-customizations[Enabling a user-managed DNS] and xref:../../../installing/installing_gcp/installing-gcp-customizations.adoc#installation-gcp-provisioning-own-dns-records_installing-gcp-customizations[Provisioning your own DNS records].
====
include::modules/creating-a-custom-ingress-controller.adoc[leveloffset=+1]