anchor.diff:   *  PG_PASSWORD
    *  PG_DATABASE
   
  -=== Password management
  -
  -Remember that if you do a database restore, you will get
  -whatever user IDs and passwords that were saved in the
  -backup.  So, if you do a restore to a new database
  -and use generated passwords, the new passwords will
  -not be the same as the passwords stored in the backup!
  +=== Password Management
  +
  +When you backup a database, the original user IDs and password credentials
  +are copied over from the original database and saved. Because of this, you
  +cannot use generated passwords as the new passwords will not be the same as the
  +passwords stored in the backup.
   
   You have various options to deal with managing your
   passwords:
  
positive.code: ./run.sh
  ....
  
  This will create the following in your Kube environment:
  
   * a Kube Job running the *crunchy-upgrade* container
   * a new data directory name *master-upgrade* found in the *pgnewdata*
  
negative.code: might be on slow networks. You can view the logs of the database pod
  to measure the copy progress.
  
  === Log Aggregation
  
  OpenShift can be configured to include the EFK stack for log aggregation.
  OpenShift Administrators can configure the EFK stack as documented
  