anchor.diff:  
   [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
  -
  -And then as shown below add the *privileged: true* to the containers `*securityContext:*` section of the yaml
  -xref:../../admin_guide/manage_scc.adoc#admin-guide-manage-scc[Managing Security Context Constraints] will provide additional information regarding SCC's.
  +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
  
positive.code: 
  [NOTE]
  ====
  To persist the gluster endpoints you will need to also create a service
  ====
  
  .GlusterFS Service Definition
  
negative.code:     Environment Variables:	<none>
  Conditions:
    Type		Status
    Initialized 	True
    Ready 	True
    PodScheduled 	True
  Volumes:
    glustervol:
      Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
  