Skip to content

Commit bb316e5

Browse files
author
Daniel Chadwick
committed
ocpbugs20186 clarify documentation about host parameters in a route
1 parent 00209eb commit bb316e5

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

modules/nw-creating-a-route.adoc

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,6 @@ The following procedure describes how to create a simple HTTP-based route to a w
1313

1414
.Prerequisites
1515

16-
1716
* You installed the OpenShift CLI (`oc`).
1817
* You are logged in as an administrator.
1918
* You have a web application that exposes a port and a TCP endpoint listening for traffic on the port.
@@ -66,15 +65,15 @@ kind: Route
6665
metadata:
6766
name: hello-openshift
6867
spec:
69-
host: hello-openshift-hello-openshift.<Ingress_Domain> <1>
68+
host: www.example.com <1>
7069
port:
7170
targetPort: 8080 <2>
7271
to:
7372
kind: Service
7473
name: hello-openshift
7574
----
76-
<1> `<Ingress_Domain>` is the default ingress domain name. The `ingresses.config/cluster` object is created during the installation and cannot be changed. If you want to specify a different domain, you can specify an alternative cluster domain using the `appsDomain` option.
77-
<2> `targetPort` is the target port on pods that is selected by the service that this route points to.
75+
<1> The `host` field is an alias DNS record that points to the service. This field can be any valid DNS name, such as `www.example.com`. The DNS name must follow DNS952 subdomain conventions. If not specified, a route name is automatically generated.
76+
<2> The `targetPort` field is the target port on pods that is selected by the service that this route points to.
7877

7978
+
8079
[NOTE]

0 commit comments

Comments
 (0)