anchor.diff:  ----
   ====
   
  -. Add the *ipfailover* service account in the *default* namespace to the *privileged* SCC: 
  +. Add the *ipfailover* service account in the *default* namespace to the *privileged* SCC:
   +
   ====
   ----
  
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: "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 must:
  
  - update the IP failover service deployment configuration to use a rolling update
  strategy, and
  - update the `*OPENSHIFT_HA_VIRTUAL_IPS*` environment variable 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:
  
  . Consider an IP failover configuration that was created using the following:
  +
  ifdef::openshift-enterprise[]
  ====
  