openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

changed note to warning and moved to top of service definition doc

Browse Source
This commit is contained in:
Frances_McDonald
2024-04-15 13:27:36 +01:00
committed by openshift-cherrypick-robot
parent e412e3927d
commit d0f2d28dd7
5 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
applications/deployments/osd-config-custom-domains-applications.adoc
View File

@@ -6,7 +6,7 @@ include::_attributes/attributes-openshift-dedicated.adoc[]
toc::[]
[NOTE]
[WARNING]
====
Starting with {product-title} 4.14, the Custom Domain Operator is deprecated. To manage Ingress in {product-title} 4.14, use the Ingress Operator. The functionality is unchanged for {product-title} 4.13 and earlier versions.
====

2
applications/deployments/rosa-config-custom-domains-applications.adoc
View File

@@ -6,7 +6,7 @@ include::_attributes/attributes-openshift-dedicated.adoc[]
toc::[]
[NOTE]
[WARNING]
====
Starting with {product-title} 4.14, the Custom Domain Operator is deprecated. To manage Ingress in {product-title} 4.14, use the Ingress Operator. The functionality is unchanged for {product-title} 4.13 and earlier versions.
====

2
cloud_experts_tutorials/cloud-experts-external-dns.adoc
View File

@@ -18,7 +18,7 @@ toc::[]
// - Dustin Scott
//---
[NOTE]
[WARNING]
====
Starting with {product-title} 4.14, the Custom Domain Operator is deprecated. To manage Ingress in {product-title} 4.14, use the Ingress Operator. The functionality is unchanged for {product-title} 4.13 and earlier versions.
====

4
modules/rosa-sdpolicy-networking.adoc
View File

@@ -15,12 +15,12 @@ This section provides information about the service definition for {product-titl
[id="rosa-sdpolicy-custom-domains_{context}"]
== Custom domains for applications
To use a custom hostname for a route, you must update your DNS provider by creating a canonical name (CNAME) record. Your CNAME record should map the OpenShift canonical router hostname to your custom domain. The OpenShift canonical router hostname is shown on the _Route Details_ page after a route is created. Alternatively, a wildcard CNAME record can be created once to route all subdomains for a given hostname to the cluster's router.
[NOTE]
[WARNING]
====
Starting with {product-title} 4.14, the Custom Domain Operator is deprecated. To manage Ingress in {product-title} 4.14 or later, use the Ingress Operator. The functionality is unchanged for {product-title} 4.13 and earlier versions.
====
To use a custom hostname for a route, you must update your DNS provider by creating a canonical name (CNAME) record. Your CNAME record should map the OpenShift canonical router hostname to your custom domain. The OpenShift canonical router hostname is shown on the _Route Details_ page after a route is created. Alternatively, a wildcard CNAME record can be created once to route all subdomains for a given hostname to the cluster's router.
[id="rosa-sdpolicy-validated-certificates_{context}"]
== Domain validated certificates

2
modules/sdpolicy-networking.adoc
View File

@@ -8,7 +8,7 @@
[id="custom-domains_{context}"]
== Custom domains for applications
[NOTE]
[WARNING]
====
Starting with {product-title} 4.14, the Custom Domain Operator is deprecated. To manage Ingress in {product-title} 4.14 or later, use the Ingress Operator. The functionality is unchanged for {product-title} 4.13 and earlier versions.
====