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: 
  [IMPORTANT]
  ====
  Please note that 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 ala `firewall-cmd` that you use).
  
  ----
  $ #  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 hostname, would have one
  generated using this default routing subdomain.
  
  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*:
  +
  .Master Configuration Snippet
  ====
  ----
  routingConfig:
    subdomain: v3.openshift.test
  ----
  ====
  +
  [NOTE]
  ====
  This change requires a restart of the master if it is running.
  ====
  +
  With the OpenShift 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
  hostname added to a namespace *mynamespace* would be:
  +
  .Generated Host Name
  ====
  ----
  no-route-hostname-mynamespace.v3.openshift.test
  
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::[]
  