anchor.diff:  
   Example of looking for the failover replica:
   ....
  -oc get pod -l name=pg-replica-rc-dc
  +oc get pod -l name=pg-slave-rc-dc
   NAME                     READY     STATUS    RESTARTS   AGE
  -pg-replica-rc-dc           1/1       Running   2          16m
  -pg-replica-rc-dc-1-96qs8   1/1       Running   1          16m
  -
  -oc get pod -l replicatype=trigger
  +pg-slave-rc-dc           1/1       Running   2          16m
  +pg-slave-rc-dc-1-96qs8   1/1       Running   1          16m
  +
  +oc get pod -l slavetype=trigger
   NAME             READY     STATUS    RESTARTS   AGE
  -pg-replica-rc-dc   1/1       Running   2          16m
  +pg-slave-rc-dc   1/1       Running   2          16m
   ....
   
   == crunchy-vacuum
  
positive.code:  * PG_DATABASE - the database to use when checking the readiness of the master
   * PG_MASTER_PORT - the PostgreSQL port to use when checking the master
   * PG_MASTER_SERVICE - the name of the master database container
   * PG_REPLICA_SERVICE - the name of the replica database container, this is
     used to know which container to trigger the failover on
  
  === Features
  
negative.code:  * SLEEP_TIME - the time to sleep in seconds between checking on the master
   * WAIT_TIME - the time to sleep in seconds between triggering the failover and updating its label (default is 40 secs)
   * PG_MASTER_SERVICE -  the master service name
   * PG_SLAVE_SERVICE - the replica service name
   * PG_MASTER_PORT - database port to use when checking the database
   * PG_MASTER_USER -  database user account to use when checking the database
     using pg_isready utility
  