anchor.diff:  *_haproxy-config.template_* file located in the *_/var/lib/haproxy/conf_*
   directory of the router container.
   
  +[[route-hostnames]]
  +
  +== Route Host Names
  +In order for services to be exposed externally, an OpenShift route allows you to
  +associate a service with an externally-reachable host name. This edge host name
  +is then used to route traffic to the service.
  +
  +.A Route with a Specified Host:
  +====
  +
  +[source,yaml]
  +----
  +apiVersion: v1
  +kind: Route
  +metadata:
  +  name: host-route
  +spec:
  +  host: www.example.com  <1>
  +  to:
  +    kind: Service
  +    name: service-name
  +----
  +<1> Specifies the externally-reachable host name used to expose a service.
  +====
  +
  +.A Route Without a Host:
  +====
  +
  +[source,yaml]
  +----
  +apiVersion: v1
  +kind: Route
  +metadata:
  +  name: no-route-hostname
  +spec:
  +  to:
  +    kind: Service
  +    name: service-name
  +----
  +====
  +
  +If a host name is not provided as part of the route definition, then
  +OpenShift automatically generates one for you. The generated host name
  +is of the form:
  +
  +----
  +*$routename[.$namespace].$suffix*
  +----
  +
  +The following example shows the OpenShift-generated host name for the above
  +configuration of a route without a host added to a namespace *my-namespace*:
  +
  +.Generated Host Name
  +====
  +
  +----
  +no-route-hostname.my-namespace.router.openshift.local <1>
  +----
  +<1> The generated host name suffix is the default routing subdomain
  +*router.openshift.local*.
  +====
  +
  +=== Custom Default Routing Subdomain
  +A cluster administrator can customize the suffix or the default routing
  +subdomain for an environment using the
  +link:../../admin_guide/master_node_configuration.html#master-configuration-files[master
  +configuration file] (the *_/etc/openshift/master/master-config.yaml_* file by
  +default). The following example shows how you can set the configured suffix to
  +*v3.openshift.test*:
  +
  +.Master Configuration Snippet
  +====
  +
  +----
  +routingConfig:
  +  subdomain: v3.openshift.test
  +----
  +====
  +
  +With the OpenShift master(s) running the above configuration, the
  +generated host name for the example of a host added to a namespace
  +*my-namespace* would be:
  +
  +.Generated Host Name
  +====
  +
  +----
  +no-route-hostname.my-namespace.v3.openshift.test
  +----
  +====
  +
   == Route Types
   Routes can be either secured or unsecured. Secure routes provide the ability to
   use several types of TLS termination to serve certificates to the client.
  
positive.code:   tls:
      termination: passthrough     <1>
  ----
  
  <1> The `*termination*` field is set to `passthrough`. No other encryption fields are needed.
  
  ====
  
  The destination pod is responsible for serving certificates for the
  
negative.code: 
  .A Secured Route Using Re-Encrypt Termination
  ====
  
  [source,yaml]
  ----
  apiVersion: v1
  