anchor.diff:  non-valid configuration is found, the apiserver will abort.  These Storage values are
   only read at apiserver start time.
   
  -==== Overriding Storage Configuration Defaults
  +=== Overriding Storage Configuration Defaults
   
   ....
   pgo create cluster testcluster --storage-config=bigdisk
  
positive.code: |Pgo.Metrics        | boolean, if set to true will cause each new cluster to include crunchy-collect as a sidecar container for metrics collection, if set to false (default), users can still add metrics on a cluster-by-cluster basis using the pgo command flag --metrics
  |======================
  
  ==== Storage Configurations
  
  Starting with release 2.5, you can now define n-number of Storage configurations
  within the *pgo.yaml* file.  Those Storage configurations follow these conventions:
   * they must have lowercase name (e.g. storage1)
   * they must be unique names (e.g. mydrstorage, faststorage, slowstorage)
  
  
negative.code: when needed (e.g. disaster recovery storage for certain backups).
  
  You can set the storage AccessMode values to the following:
  
  * *ReadWriteMany* - mounts the volume as read-write by many nodes
  * *ReadWriteOnce* - mounts the PVC as read-write by a single node
  * *ReadOnlyMany* - mounts the PVC as read-only by many nodes
  