anchor.diff:  
   If you see a line returned from that query it means the primary is replicating
   to the replica.  Try creating some data on the primary:
  -
   ....
   psql -h ms-primary -U postgres postgres -c 'create table foo (id int)'
   psql -h ms-primary -U postgres postgres -c 'insert into foo values (1)'
  
positive.code: pgbadger reads the log files from a database to product an HTML report
  that shows various PostgreSQL statistics and graphs.
  
  To run the example, modify the run-badger.sh script to refer to the
  Docker container that you want to run pgbadger against, also referring
  to the container's data directory, then run the example as follows:
  ....
  cd $CCPROOT/examples/docker/basic
  ./run.sh
  cd $CCPROOT/examples/docker/badger
  ./run.sh
  ....
  
negative.code:  * the /pgdata directory is empty
   * the /backups directory contains a valid postgresql.conf file
  
  === pgbackrest
  
  Starting in release 1.3.1, the *pgbackrest* utility has been
  added to the crunchy-postgres container.  See the
  link:backrest.adoc[pgbackrest Documentation] for details
  on how this feature works within the Crunchy Container Suite.
  
  === pgadmin4
  
  This example deploys the pgadmin4 (beta4) web user interface
  for PostgreSQL.
  
  After running the example, you should be able to browse to http://127.0.0.1:5050
  and log into the web application using a user ID of *admin@admin.org*
  and password of *password*. If you are running this example using Kubernetes or
  OpenShift, replace *127.0.0.1* with the IP address of the created service.
  
  The example uses pgadmin4 configuration files which are mounted
  at an NFS mount point. This NFS data directory is mounted into
  the container and used by the pgadmin4 application to persist
  Metadata.
  
  See the link:http://pgadmin.org[pgadmin4 documentation] for more details.
  
  To shutdown the instance and remove the container for each example, run the following:
  ....
  ./cleanup.sh
  ....
  
  ==== Docker
  
  To run this example, run the following:
  ....
  cd $CCPROOT/examples/docker/pgadmin4
  ./run.sh
  ....
  
  ==== Kubernetes
  
  Start the container as follows:
  ....
  cd $CCPROOT/examples/kube/pgadmin4
  ./run.sh
  ....
  
  ==== OpenShift
  
  To run this example, run the following:
  ....
  cd $CCPROOT/examples/openshift/pgadmin4
  ./run.sh
  ....
  
  === Proxy
  
  A *crunchy-proxy* example is provided that will run a container that creates a special
  purpose proxy to the primary and replica example provided in the *primary-replica* example.
  
  *crunchy-proxy* offers a high performance alternative to
  pgbouncer and pgpool.
  
  The proxy example copies a configuration file to the PV_PATH
  and starts up the *crunchy-proxy* within a Deployment.
  It then reads the configuration file from a */config* volume
  mount and begins execution.
  
  The proxy will listen on port 5432 as specified in the
  configuration file.  The example creates a Service named
  *crunchy-proxy* that you can use to access the configured
  PostgreSQL backend containers from the *primary-replica* example.
  
  SQL "reads" will be sent to the PostgreSQL replica database if your
  SQL includes the *crunchy-proxy* read annotation.  SQL statements
  that do not include the read annotation will be sent to the primary
  database container within the PostgreSQL cluster.
  
  See this link for details on the *crunchy-proxy*:
  https://github.com/CrunchyData/crunchy-proxy
  
  To shutdown the instance and remove the container for each example, run the following:
  ....
  ./cleanup.sh
  ....
  
  ==== Docker
  
  You can create the proxy by running:
  ....
  cd $CCPROOT/examples/docker/crunchy-proxy
  ./run.sh
  ....
  
  This proxy will listen on localhost:12432.  You can access the
  *primary-replica* cluster through the following:
  ....
  psql -h localhost -p 12432 -U postgres postgres
  ....
  
  ==== Kubernetes
  
  *Note*: If you run the example in minikube, you will need to manually
  copy the crunchy-proxy-config.json file to a file on
  the minikube named */data/config.json*.
  
  Start by running the proxy container:
  ....
  cd $CCPROOT/examples/kube/crunchy-proxy
  ./run.sh
  ....
  
  Test the proxy by running psql commands via the proxy connection:
  ....
  psql -h crunchy-proxy -U postgres postgres
  ....
  
  ==== OpenShift
  
  Start by running the proxy container:
  ....
  cd $CCPROOT/examples/openshift/crunchy-proxy
  ./run.sh
  ....
  
  Test the proxy by running psql commands via the proxy connection:
  ....
  psql -h crunchy-proxy -U postgres postgres
  ....
  
  === pgpool
  
  An example is provided that will run a pgpool container in conjunction with the
  primary and replica example (*primary-replica*) provided above.
  
  You can execute both INSERT and SELECT statements after connecting to pgpool.
  The container will direct INSERT statements to the primary and SELECT statements
  will be sent round-robin to both primary and replica.
  
  The container creates a default database called *userdb*, a default user called
  *testuser* and a default password of *password*.
  
  To shutdown the instance and remove the container for each example, run the following:
  ....
  ./cleanup.sh
  ....
  
  ==== Docker
  
  Create the container as follows:
  ....
  cd $CCPROOT/examples/docker/pgpool
  ./run.sh
  ....
  
  Enter the following command to connect to the pgpool container that is
  mapped to your local port 12003:
  ....
  psql -h localhost -U testuser -p 12003 userdb
  ....
  
  ==== Kubernetes
  
  Running the example:
  ....
  