anchor.diff:  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 
  +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. 
  +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.
  
positive.code: 
  === High Availability
  You can link:../../admin_guide/high_availability.html[set up a highly-available
  router] on your OpenShift cluster using IP failover.
  
  [[customizing-the-router-service-ports]]
  
  === Customizing the Router Service Ports
  
  You can customize the service ports that a template router binds to, by
  setting the environment variables `ROUTER_SERVICE_HTTP_PORT` and
  `ROUTER_SERVICE_HTTPS_PORT`. This can be done by creating a template router
  and then editing its deployment config.
  
  ====
  The following example creates a router deployment with `0` replicas and
  customizes the router service HTTP and HTTPS ports and then scales it
  appropriately (to `1` replica).
  ----
  $ oadm router --replicas=0
  $ oc env dc/router ROUTER_SERVICE_HTTP_PORT=10080  \
  
negative.code: ====
  
  [[forcing-route-hostnames-to-a-custom-routing-subdomain]]
  === 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 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
  