anchor.diff:  ----
   $ oc get endpoints
   NAME                ENDPOINTS                             AGE
  -docker-registry     10.128.0.3:5000                       4h
  +docker-registry     10.1.0.3:5000                         4h
   glusterfs-cluster   192.168.122.221:1,192.168.122.222:1   11s
   kubernetes          172.16.35.3:8443                      4d
   ----
   ====
   
   [[gfs-creating-persistent-volume]]
  -
   === Creating the Persistent Volume
   
  -You must define your persistent volume in an object definition before creating
  +The storage admin next defines the persistent volume (PV) in an object definition before creating
   it in OpenShift:
   
   .Persistent Volume Object Definition Using GlusterFS
  
positive.code: apiVersion: v1
  kind: Endpoints
  metadata:
    name: glusterfs-cluster
  subsets:
    - addresses:
        - ip: 192.168.122.221 <1>
      ports:
        - port: 1
    - addresses:
        - ip: 192.168.122.222 <1>
      ports:
        - port: 1
  ----
  <1> The `*ip*` values must be the actual IP addresses of a Gluster server, not
  fully-qualified host names. This requirement could change in future releases.
  ====
  
  Save your endpoints definition to a file, for example
  *_gluster-endpoints.yaml_*, then create the endpoints:
  
  ====
  
negative.code: 
  [source,yaml]
  ----
  apiVersion: v1
  kind: PersistentVolume
  metadata:
    name: gluster-default-volume <1>
  spec:
    capacity:
      storage: 2Gi <2>
    accessModes: <3>
      - ReadWriteMany
    glusterfs: <4>
      endpoints: glusterfs-cluster <5>
      path: myVol1 <6>
      readOnly: false
    persistentVolumeReclaimPolicy: Recycle
  ----
  <1> The name of the volume. This is how it is identified via
  link:../../architecture/additional_concepts/storage.html[persistent volume
  claims] or from pods.
  <2> The amount of storage allocated to this volume.
  <3> `accessModes` are used as labels to match a PV and a PVC. They currently
  do not define any form of access control.
  <4> The volume type being used, in this case the *glusterfs*
  plug-in.
  <5> The endpoints name that defines the Gluster cluster.
  created in link:#creating-gluster-endpoints[Creating Gluster Endpoints].
  <6> The Gluster volume that will be accessed, as shown in the `gluster volume status`
  command.
  ====
  
  Save your definition to a file, for example *_gluster-pv.yaml_*, and create the
  