anchor.diff:  ====
   endif::[]
   
  +As with the HAProxy router, the `oadm router` command creates the service and
  +deployment configuration objects, and thus the replication controllers and
  +pod(s) in which the F5 router itself runs. The replication controller restarts
  +the F5 router in case of crashes. Because the F5 router is watching routes,
  +endpoints, and nodes and configuring *F5 BIG-IP®* accordingly, running the F5
  +router in this way, along with an appropriately configured *F5 BIG-IP®*
  +deployment, should satisfy high-availability requirements.
  +
   [[f5-router-partition-paths]]
   == F5 Router Partition Paths
   Partition paths allow you to store your {product-title} routing configuration in
  
positive.code: ====
  endif::[]
  
  The F5 router plug-in is provided as a container image and run as a pod, just like
  the xref:../../install_config/router/default_haproxy_router.adoc#install-config-router-default-haproxy[default HAProxy router]. Deploying the F5 router is
  done similarly as well, using the `oadm router` command but providing additional
  flags (or environment variables) to specify the following parameters for the *F5
  BIG-IP®* host:
  
  [[f5-router-flags]]
  
negative.code: Native Integration] section of the Routes topic.
  ====
  
  ifdef::openshift-enterprise[]
  As of {product-title} version 3.4, using native integration of F5 with
  {product-title} does not require configuring a ramp node for F5 to be able to
  reach the pods on the overlay network as created by OpenShift SDN.
  endif::[]
  ifdef::openshift-origin[]
  With native integration of F5 with {product-title}, you do not need to
  configure a ramp node for F5 to be able to reach the pods on the overlay network
  as created by OpenShift SDN.
  endif::[]
  
  The F5 controller pod needs to be launched with enough information so that it can
  successfully directly connect to pods.
  