anchor.diff:  |all        | compile all binaries and build all images
   |setup        | fetch the dependent packages required to build with
   |deployoperator        | deploy the Operator (apiserver and postgers-operator) to Kubernetes
  -|main        | compile the postgres-operator 
  +|main        | compile the postgres-operator
   |runmain        | locally execute the postgres-operator
   |pgo        | build the pgo binary
  -|runpgo        | run the pgo binary 
  +|runpgo        | run the pgo binary
   |runapiserver        | run the apiserver binary outside of Kube
   |clean        | remove binaries and compiled packages, restore dependencies
   |operatorimage        | compile and build the postgres-operator Docker image
  
positive.code: === Configure Persistent Storage
  
  The default Operator configuration is defined to use a HostPath
  persistence configuration.  
  
  There are example scripts provided that will create PV and PVC resources
  that can be used in your testing. 
  
  These example scripts can create sample HostPath and NFS volumes. 
  
  To create sample HostPath Persistent Volumes and CLaims use the following scripts:
  ....
  
negative.code: Note that the default *pgo.yaml* file assumes you are going to use *HostPath* Persistent Volumes for
  your storage configuration.  Adjust this file for NFS or other storage configurations.
  
  The version of PostgreSQL container the Operator will deploy is determined
  by the *CCPImageTag* setting in the *$COROOT/conf/apiserver/pgo.yaml*
  configuration file.  By default, this value is set to the latest
  release of the Crunchy Container Suite.
  
  