anchor.diff:  ====
   
   [[forcing-route-hostnames-to-a-custom-routing-subdomain]]
  -
  -=== Forcing Route Hostnames to a Custom Routing Subdomain
  -
  -If an adminstrator wishes to restrict all routes to a specific routing
  -subdomain, they can do this by passing the `--force-subdomain` option to the
  -`oadm router` command. This forces the router to override any hostnames
  -specified in a route and generate one based on the template provided to the
  +=== Forcing Route Host Names to a Custom Routing Subdomain
  +If an administrator wants to restrict all routes to a specific routing
  +subdomain, they can pass the `--force-subdomain` option to the `oadm
  +router` command. This forces the router to override any host names specified in
  +a route and generate one based on the template provided to the
   `--force-subdomain` option.
   
  -====
  -The following example runs a router which will override the route hostnames
  -using a custom subdomain template `${name}-${namespace}.apps.example.com`.
  +The following example runs a router, which overrides the route host names using
  +a custom subdomain template `${name}-${namespace}.apps.example.com`.
  +
  +====
   ----
   $ oadm router --force-subdomain='${name}-${namespace}.apps.example.com'
   ----
   ====
   
   [[using-wildcard-certificates]]
  -
   === Using Wildcard Certificates
   
   A TLS-enabled route that does not include a certificate uses the router's
  
positive.code: Partition paths allow you to store your OpenShift routing configuration in a
  custom *F5 BIG-IP®* administrative partition, instead of the default */Common*
  partition. You can use custom administrative partitions to secure *F5 BIG-IP®*
  environments. This means that an OpenShift-specific configuration stored in 
  *F5 BIG-IP®* system objects reside within a logical container, allowing
  administrators to define access control policies on that specific administrative
  partition. 
  
  See the
  link:https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/tmos_management_guide_10_0_0/tmos_partitions.html[*F5 BIG-IP®* documentation] for more information about administrative partitions.
  
negative.code: 
  [IMPORTANT]
  ====
  If you do customize the template router service ports, you will also need to
  ensure that the nodes where the router pods run have those custom ports opened
  in the firewall (either via *Ansible* or *iptables*, or any other custom method
  that you use via *firewall-cmd*).
  ====
  
  The following is an example using *iptables* to open the custom router service
  ports.
  
  ====
  ----
  $ iptables -A INPUT -p tcp --dport 10080 -j ACCEPT
  $ iptables -A INPUT -p tcp --dport 10443 -j ACCEPT
  ----
  ====
  
  [[customizing-the-default-routing-subdomain]]
  === Customizing the Default Routing Subdomain
  You can customize the default routing subdomain by modifying the master
  configuration file. Routes that do not specify a host name would have one
  generated using this default routing subdomain.
  
  [[modifying-the-master-configuration-file]]
  ==== Modifying the Master Configuration file
  You can customize the suffix used as the default routing subdomain for your
  environment using the
  link:../../install_config/master_node_configuration.html#master-configuration-files[master
  configuration file] (the *_/etc/origin/master/master-config.yaml_* file by
  default).
  
  The following example shows how you can set the configured suffix to
  *v3.openshift.test*:
  
  ====
  ----
  routingConfig:
    subdomain: v3.openshift.test
  ----
  ====
  
  [NOTE]
  ====
  This change requires a restart of the master if it is running.
  ====
  
  With the {product-title} master(s) running the above configuration, the
  link:../../architecture/core_concepts/routes.html#route-hostnames[generated host
  name] for the example of a route named *no-route-hostname* without a
  host name added to a namespace *mynamespace* would be:
  
  ====
  ----
  no-route-hostname-mynamespace.v3.openshift.test
  