anchor.diff:  see if the master is responding.  If the master doesn't respond, the watcher
   will perform the following logic:
   
  - * log into openshift using the service account
  + * log into Openshift using the service account
    * set its current project
    * find the first replica pod
    * delete the master service saving off the master service definition
    * create the trigger file on the first replica pod
    * wait 20 seconds for the failover to complete on the replica pod
  - * edit the replica pod's lable to match that of the master
  + * edit the replica pod's label to match that of the master
    * recreate the master service using the stored service definition
    * loop through the other remaining replica and delete its pod
   
  
positive.code: 
  To test it out, delete the master pod and view the watch pod log:
  ....
  oc delete pod pg-master-rc-dc
  oc logs watch
  oc get pod
  ....
  
negative.code: 
  Next, create an Openshift service account which is used by the crunchy-watch
  container to perform the failover, also set policies that allow the
  service account the ability to edit resources within the Openshift and
  default projects :
  
  ....
  