text: **Persistent Volumes**
  PersistentVolumes (PV) objects provide pods with non-ephemeral storage by configuring and 
  encapsulating underlying storage sources. A PersistentVolumeClaim (PVC) abstracts an 
  underlying PV to provide provider-independent storage to OpenShift resources. When 
  successfully fulfilled by the system, a PVC mounts the persistent storage to a specific 
  directory (mountPath) within one or more pods. From the container perspective, the 
  mountPath is connected to the underlying storage mount points by a regular bind mount. 
  
  **FlexVolumes**
  FlexVolume is known as an*out-of-tree plug-in interface*because it is developed outside the 
  main Kubernetes source code. The FlexVolume interface enables users to write their own 
  drivers. These drivers can be written in any programming or scripting language. 
  
  When an application that is running on OpenShift needs a persistent volume, it submits a 
  persistent volume claim to the PowerVC FlexVolume driver. The PowerVC FlexVolume call is 
  translated into a Cinder API call to create a volume. When the volume is ready, it is presented 
  back to OpenShift and attached to the requesting pod. 
  
  The persistent volume claim needs to include only the volume size and access mode. The 
  backend implementation information about how and where the volume is created are handled 
  by PowerVC. The OpenShift API abstracts them from the user that is making the resource 
  claim. 