Merge pull request #44580 from ahardin-rh/issue-44450

Issue#44450, clarifying ingress usage

Author: ahardin-rh

modules/nw-ingress-creating-a-route-via-an-ingress.adoc

@@ -6,10 +6,7 @@
 [id="nw-ingress-creating-a-route-via-an-ingress_{context}"]
 = Creating a route through an Ingress object
 
-Some ecosystem components have an integration with Ingress resources but not with
-route resources. To cover this case, {product-title} automatically creates
-managed route objects when an Ingress object is created. These route objects are deleted
-when the corresponding Ingress objects are deleted.
+Some ecosystem components have an integration with `Ingress` resources but not with `Route` resources. To cover this case, {product-title} automatically creates managed route objects when an Ingress object is created. These route objects are deleted when the corresponding `Ingress` objects are deleted.
 
 .Procedure
 
@@ -26,7 +23,7 @@ metadata:
     route.openshift.io/termination: "reencrypt" <1>
 spec:
   rules:
-  - host: www.example.com
+  - host: www.example.com <2>
     http:
       paths:
       - backend:
@@ -42,9 +39,9 @@ spec:
     secretName: example-com-tls-certificate
 ----
 +
-<1> The `route.openshift.io/termination` annotation can be used to configure the `spec.tls.termination` field of the `Route`
-as `Ingress` has no field for this. The accepted values are `edge`, `passthrough` and `reencrypt`. All
-other values are silently ignored. When the annotation value is unset, `edge` is the default route. The TLS certificate details must be defined in the template file to implement the default edge route.
+<1> The `route.openshift.io/termination` annotation can be used to configure the `spec.tls.termination` field of the `Route` as `Ingress` has no field for this. The accepted values are `edge`, `passthrough` and `reencrypt`. All other values are silently ignored. When the annotation value is unset, `edge` is the default route. The TLS certificate details must be defined in the template file to implement the default edge route and to prevent producing an insecure route.
+<2> When working with an `Ingress` object, you must specify an explicit host name, unlike when working with routes. You can use the `<host_name>.<cluster_ingress_domain>` syntax, for example `apps.openshiftdemos.com`, to take advantage of the `*.<cluster_ingress_domain>` wildcard DNS record and serving certificate for the cluster. Otherwise, you must ensure that there is a DNS record for the chosen hostname.
+
 
 .. If you specify the `passthrough` value in the `route.openshift.io/termination` annotation, set `path` to `''` and `pathType` to `ImplementationSpecific` in the spec:
 +