anchor.diff:  +
   [IMPORTANT]
   ====
  -* Use RWX if you want the persistent volume (PV) that fulfills this PVC to be mounted to multiple Pods on multiple nodes in the cluster.
  -
  -* Use RWO mode if you want to prevent additional Pods from being dynamically provisioned.
  +Use RWX if you want the persistent volume (PV) that fulfills this PVC to be mounted to multiple pods on multiple nodes in the cluster.
   ====
   
   . Define the size of the storage claim.
  
positive.code: +
  The `pvc-manila` shows that it is `Bound`.
  
  You can now use the new PVC to configure a Pod.
  
negative.code: [id="persistent-storage-csi-manila-dynamic-provisioning_{context}"]
  = Dynamically provisioning Manila CSI volumes
  
  {product-title} installs a storage class for each available Manila share type.
  
  The YAML files that are created are completely decoupled from Manila and from its Container Storage Interface (CSI) plug-in. As an application developer, you can dynamically provision ReadWriteMany (RWX) storage and deploy pods with applications that safely consume the storage using YAML manifests.
  
  You can use the same pod and persistent volume claim (PVC) definitions on-premise that you use with {product-title} on AWS, GCP, Azure, and other platforms, with the exception of the storage class reference in the PVC definition.
  
  [NOTE]
  ====
  Manila service is optional. If the service is not enabled in {rh-openstack-first}, the Manila CSI driver is not installed and the storage classes for Manila are not created.
  ====
  
  .Prerequisites
  
  * {rh-openstack} is deployed with appropriate Manila share infrastructure so that it can be used to dynamically provision and mount volumes in {product-title}.
  
  .Procedure (UI)
  
  