anchor.diff:  psql -c 'table testtable' -U primary -h m-s-rc-pvc-replica postgres
   ....
   
  -=== Master / Replica Deployment
  +=== Primary / Replica Deployment
   
   
   ==== Kubernetes
  
positive.code: pod for the primary, and will be able to start up immediately since
  we are using the same /pgdata/primary-dc data directory.
  
  === Master using PVC
  
  
  ==== OpenShift
  
negative.code: psql -h ms-replica -U postgres postgres -c 'table foo'
  ....
  
  ==== Helm
  
  This example creates a simple Postgres streaming replication deployment with a
  primary (read-write), and a single asynchronous replica (read-only). You can
  scale up the number of replicas dynamically.
  
  To deploy a primary and replica database cluster using a Helm chart within your
  Kubernetes cluster, you can execute the following:
  
  ....
  cd $CCPROOT/examples/kube/primary-replica
  helm install primary-replica --name crunchydata
  ....
  
  To verify everything is up and running correctly, you can view the created pods
  as follows:
  
  ....
  kubectl get pod | grep crunchydata
  ....
  
  For more in-depth troubleshooting, you can view the logs or describe the state of the
  pod:
  
  ....
  kubectl logs crunchydata-crunchy-primary
  kubectl describe pod crunchydata-crunchy-primary
  ....
  
  After installing the Helm chart, you will see the following services:
  ....
  $ kubectl get services
  NAME                          TYPE        CLUSTER-IP   EXTERNAL-IP      PORT(S)    AGE
  crunchydata-crunchy-primary   ClusterIP   10.0.0.99    <none>           5432/TCP   22m
  crunchydata-crunchy-replica   ClusterIP   10.0.0.253   <none>           5432/TCP   22m
  kubernetes                    ClusterIP   10.0.0.1     <none>           443/TCP    7h
  ....
  
  It takes about a minute for the replica to begin replicating with the
  primary.  To test out replication, see if replication is underway
  with this command, enter *password* for the password when prompted:
  ....
  psql -h crunchydata-crunchy-primary -U postgres postgres -c 'table pg_stat_replication'
  ....
  
  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 crunchydata-crunchy-primary -U postgres postgres -c 'create table foo (id int)'
  psql -h crunchydata-crunchy-primary -U postgres postgres -c 'insert into foo values (1)'
  ....
  
  Then verify that the data is replicated to the replica:
  ....
  psql -h crunchy-replica -U postgres postgres -c 'table foo'
  ....
  
  You can scale up the number of read-only replicas by running
  the following kubernetes command:
  ....
  kubectl scale deployment crunchy-replica --replicas=2
  ....
  
  It takes 60 seconds for the replica to start and begin replicating
  from the primary.
  
  
  ==== OpenShift
  
  