anchor.diff:   to define and create the PVC.
   
   ----
  -# oc create  -f glusterfs-ep.yaml
  +# oc create -f glusterfs-ep.yaml
   endpoints "glusterfs-cluster" created
   # oc create -f glusterfs-pv.yaml
   persistentvolume "gluster-volume" created
  
positive.code:   accessModes:
      - ReadWriteMany
    glusterfs:
      endpoints: glusterfs-cluster
      path: myVol1
      readOnly: false
    persistentVolumeReclaimPolicy: Recycle
  ----
  <1> Use labels to identify common attributes or characteristics shared among
   volumes. In this case, we assume that this glusterFS volume is a member of a
   fictional `gold-tier` level of storage.
  ====
  
  [[binding-pv-by-label-pvc-with-selectors]]
  ==== Persistent Volume Claim with Selectors
  
  It is important to note that a PVC will attempt to match *all* labels included
  in the *selectors* stanza. If no PV exists with an identical set of labels, the
  PVC will remain unbound.
  
  .glusterfs-pvc.yaml
  ====
  
negative.code: NAME              STATUS     VOLUME           CAPACITY   ACCESSMODES               AGE
  gluster-claim     Bound      gluster-volume   2Gi        RWX                       7s
  ----
  
  [NOTE]
  ====
  PVCs are local to a project; whereas PVs are a cluster-wide, global resource. Developers
  and non-admin users may not have access to see all (or any) of the available PVs.
  ====
  