anchor.diff:  
   .HAProxy Router Data Flow
   image:router_model.png[HAProxy Router Data Flow]
  +====
  +
  +*Sticky Sessions*
  +
  +Implementing sticky sessions is up to the underlying router configuration.  The default HAProxy
  +template implements sticky sessions using the `balance source` directive which balances based
  +on the source IP.  In addition, the template router plugin will provide the service name and
  +namespace to the underlying implementation.  This can be used for more advanced configuration
  +such as implementing stick-tables that synchronize between a set of peers. For details on the
  +implementation you may inspect the `haproxy-config.template` located in the `/var/lib/haproxy/conf`
  +directory of your router container.
   
   == Highly-available Routers
   You can configure a highly-available router setup by running multiple instances
  
positive.code: $ ping hello-openshift.shard1.v3.rhcloud.com
  [...]
  ----
  
  == High Availability Router Setup with IP Failover
  The following steps describe how to setup a highly available router environment with IP failover in a 3-step operation:
  
negative.code: they are given one of the many records, in order, as a round robin scheme.
  
  [NOTE]
  The procedure below uses wildcard DNS with multiple A records to achieve the
  desired round robin. The wildcard could be further distributed into shards with:
  
  ====
  ****
  `*._<shard>_`
  ****
  