anchor.diff:  == Overview
   This topic provides an end-to-end example for binding
   xref:../../architecture/additional_concepts/storage.adoc#persistent-volume-claims[persistent
  -volume claims] (Persistent Volume Claims, PVCs) to
  +volume claims (PVCs)] to
   xref:../../architecture/additional_concepts/storage.adoc#persistent-volumes[persistent
  -volumes] (Persistent Volumes, PVs), by defining labels in the PV and matching selectors in the PVC.
  +volumes (PVs)], by defining labels in the PV and matching selectors in the PVC.
   This feature is available for all xref:../persistent_storage/index.adoc#[storage
  -options]. It is assumed that a {product-title} cluster contains persistent storage
  -resources which are available for binding by PVCs.
  +options]. It is assumed that a {product-title} cluster contains persistent
  +storage resources which are available for binding by PVCs.
   
   *A Note on Labels and Selectors*
   
  -Labels are an {product-title} feature that support user-defined tags (key-value pairs)
  -as part of an object's specification. Their primary purpose is to enable the
  -arbitrary grouping of objects by defining identical labels among them. These
  +Labels are an {product-title} feature that support user-defined tags (key-value
  +pairs) as part of an object's specification. Their primary purpose is to enable
  +the arbitrary grouping of objects by defining identical labels among them. These
   labels can then be targeted by selectors to match all objects with specified
   label values. It is this functionality we will take advantage of to enable our
   PVC to bind to our PV. For a more in-depth look at labels, see
  
positive.code: 
  [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.
  ====
  
negative.code:   persistentVolumeReclaimPolicy: Retain
  ----
  <1> Use labels to identify common attributes or characteristics shared among
   volumes. In this case, we defined the Gluster volume to have a custom attribute
   (key) named *storage-tier* with a value of *gold* assigned. A claim will be
   able to select a PV with `*storage-tier=gold*` to match this PV.
  <2> Endpoints define the Gluster trusted pool and are discussed below.
  ====
  
  [[binding-pv-by-label-pvc-with-selectors]]
  