anchor.diff:  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
  
positive.code: "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[]
  ====
  
negative.code: ====
  endif::[]
  
  For details on how to dynamically update the virtual IP addresses for high
  availability, see
  link:#dynamically-updating-vips-for-a-highly-available-service[Dynamically
  Updating Virtual IPs for a Highly-available Service].
  
  === Configuring a Highly-available Network Service [[ip-failover]]
  
  