instruction: Configure Kubernetes persistent volume storage with subPath
output: ```dockerfile
  from the
  API that allows reclamation of the resource. The reclaim policy for a PersistentVolume
  tells the cluster what to do with the volume after it has been released of its claim.
  Currently, volumes can either be Retained, Recycled, or Deleted.
  Retain
  The Retain reclaim policy allows for manual reclamation of the resource.
  When the PersistentVolumeClaim is deleted, the PersistentVolume still exists
  and the volume is considered "released". But it is not yet available for
  another claim because the previous claimant's data remains on the volume.
  An administrator can manually reclaim the volume with the following steps.
  
  Delete the PersistentVolume. The associated storage asset in external infrastructure
  still exists after the PV is deleted.
  Manually clean up the data on the associated storage asset accordingly.
  Manually delete the associated storage asset.
  
  If you want to reuse the same storage asset, create a new PersistentVolume with
  the same storage asset definition.
  Delete
  For volume plugins that support the Delete reclaim policy, deletion removes
  both the PersistentVolume object
  ```