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: Native Integration] section of the Routes topic.
  ====
  
  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.
  
  The F5 controller pod needs to be launched with enough information so that it can
  successfully directly connect to pods.
  
negative.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]. 
  
  [[install-router-f5-prerequisites]]
  == Prerequisites
  
  When deploying the F5 router plug-in, ensure you meet the following
  requirements:
  
  . An F5 host IP and credentials
  . The name of the virtual servers (for both HTTP and HTTPS)
  . The private key to the F5 instance
  . The host-internal IP and VXLAN gateway
  ifdef::openshift-origin[]
  . Ensure you have xref:../../install_config/router/index.adoc#creating-the-router-service-account[created the router service account].
  endif::[]
  
  [[deploying-the-f5-router]]
  == Deploying the F5 Router
  
  [IMPORTANT]
  ====
  The F5 router must be run in privileged mode, because route certificates are
  copied using the `scp` command:
  
  ----
  $ oadm policy remove-scc-from-user hostnetwork -z router
  $ oadm policy add-scc-to-user privileged -z router
  ----
  ====
  
  Deploy the F5 router with the `oadm router` command, but provide additional
  flags (or environment variables) specifying the following parameters for the *F5
  BIG-IP®* host:
  
  [[f5-router-flags]]
  