anchor.diff:  ====
   
   [[complete-example-using-gusterfs-creating-the-gluster-endpoints]]
  -== Creating the Gluster Endpoints
  +== Creating the Gluster Endpoints and Gluster Service for Persistence
   
   The named endpoints define each node in the Gluster-trusted storage pool:
   
  
positive.code: <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.
  ====
  
  Save the PV definition to a file, for example *_gluster-pv.yaml_*,
  
negative.code: spec:
    containers:
    - name: gluster-pod1
      image: nginx       <2>
      ports:
      - name: web
        containerPort: 80
      securityContext:
        privileged: true
      volumeMounts:
      - name: gluster-vol1 <3>
        mountPath: /usr/share/nginx/html <4>
        readOnly: false
    securityContext:
      supplementalGroups: [590]       <5>
    volumes:
    - name: gluster-vol1   <3>
      persistentVolumeClaim:
        claimName: gluster-claim      <6>
  ----
  <1> The name of this pod as displayed by `oc get pod`.
  <2> The image run by this pod. In this case, we are using standard ngnix image.
  <3> The name of the volume. This name must be the same in both the
  `*containers*` and `*volumes*` sections.
  <4> The mount path as seen in the container.
  <5> The SupplementalGroup ID (Linux Groups) to be assigned at the pod level 
  and as discussed this should match the POSIX permissions on the gluster volume.
  <6> The PVC that is bound to the Gluster cluster.
  ====
  
  