anchor.diff:      Environment Variables:	<none>
   Conditions:
     Type		Status
  -  Initialized 	True 
  -  Ready 	True 
  -  PodScheduled 	True 
  +  Initialized 	True
  +  Ready 	True
  +  PodScheduled 	True
   Volumes:
     glustervol:
       Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
  
positive.code: plug-in is defined.
  <5> This references the endpoints named above.
  <6> This is the Gluster volume name, preceded by `/`.
  <7> A volume reclaim policy of *retain* indicates that the volume will be
  preserved after the pods accessing it terminate. Accepted values include (Retain, Delete and Recycle)
  ====
  
  Save the PV definition to a file, for example *_gluster-pv.yaml_*,
  
negative.code: 
  [NOTE]
  ====
  The NGINX image may require to run in privileged mode to create the mount and
  run properly. An easy way to accomplish this is to simply add your user to the
  *privileged* Security Context Constraint (SCC):
  ----
  $ oadm policy add-scc-to-user privileged myuser
  ----
  
  Then, add the *privileged: true* to the containers `*securityContext:*` section
  of the YAML file (as seen in the example below).
  
  xref:../../admin_guide/manage_scc.adoc#admin-guide-manage-scc[Managing Security
  Context Constraints] provides additional information regarding SCCs.
  ====
  
  .Pod Object Definition using NGINX image
  