anchor.diff:  instance is "unreachable", perhaps due to a node failure, Keepalived ensures
   that the VIPs automatically float amongst the group of nodes labeled
   "ha-cache=geo" and the service is still reachable via the virtual IP addresses.
  +
  +[[dynamically-updating-vips-for-a-highly-available-service]]
  +
  +=== Dynamically Updating Virtual IPs for a Highly-available Service
  +The default deployment strategy for the IP failover service is to recreate
  +the deployment. In order to dynamically update the virtual IPs for a highly
  +available routing service with minimal or no downtime, you will need to
  +update the IP failover service deployment config to use a rolling update
  +strategy and update the environment variable `OPENSHIFT_HA_VIRTUAL_IPS` with
  +the updated list or sets of virtual IP addresses.
  +
  +The following example shows how to dynamically update the deployment
  +strategy and the virtual IP addresses:
  ++
  +ifdef::openshift-enterprise[]
  +====
  +----
  +$ oadm ipfailover ipf-ha-router-us-west \
  +    --replicas=5 --watch-port=80 \
  +    --selector="ha-router=geo-us-west" \
  +    --virtual-ips="10.245.2.101-105" \
  +    --credentials=/etc/origin/master/openshift-router.kubeconfig \
  +    --service-account=ipfailover --create
  +----
  +====
  +endif::[]
  +ifdef::openshift-origin[]
  +====
  +----
  +$ oadm ipfailover ipf-ha-router-us-west \
  +    --replicas=5 --watch-port=80 \
  +    --selector="ha-router=geo-us-west" \
  +    --virtual-ips="10.245.2.101-105" \
  +    --credentials="$KUBECONFIG" \
  +    --service-account=ipfailover --create
  +----
  +====
  +endif::[]
  +----
  +$ oc edit dc/ipf-ha-router-us-west
  +
  +$ #  Update Spec.Strategy.Type from "Recreate" to "Rolling".
  +$ #  Example:
  +$ #     - Spec:
  +$ #       ...
  +$ #       Strategy:
  +$ #         Type: Rolling
  +$ #         ...
  +
  +$ #  Update the environment variable OPENSHIFT_HA_VIRTUAL_IPS to contain
  +$ #  the additional virtual IP addresses.
  +$ #  Example:
  +$ #     - name: OPENSHIFT_HA_VIRTUAL_IPS
  +$ #       value: 10.245.2.101-105,10.245.2.110,10.245.2.201-205
  +----
  
positive.code: the service being setup for failover, it is possible to target the service to
  run on one or more, or even all, of the labeled nodes.
  ====
  
  . Finally, configure the VIPs and failover for the nodes labeled with
  *ha-router=geo-us-west* in the first step. Ensure the number of replicas match
  the number of nodes and that they satisfy the label setup in the first step. The
  
negative.code: ====
  endif::[]
  
  
  For details on how to dynamically update the virtual IP addresses for a
  highly available, see
  link:#dynamically-updating-vips-for-a-highly-available-service [dynamically updating the virtual IPs]
  
  === Configuring a Highly-available Network Service [[ip-failover]]
  
  The following steps describe how to set up a highly-available IP-based network
  