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: ====
  
  [[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
  `--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`.
  ----
  $ 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
  
negative.code: endif::[]
  - Deploy an link:docker_registry.html[integrated Docker registry].
  ifdef::openshift-origin[]
  - link:../../install_config/imagestreams_templates.html[Populate your OpenShift installation]
  with a useful set of Red Hat-provided image streams and templates.
  endif::[]
  