instruction: Configure Kubernetes persistent volume storage with subPath
output: ```dockerfile
  from the same
  volume on the storage system and therefore cannot be expressed by using the same
  StorageClass of a PersistentVolumeClaim.
  Volume snapshots provide Kubernetes users with a standardized way to copy a volume's
  contents at a particular point in time without creating an entirely new volume. This
  functionality enables, for example, database administrators to backup databases before
  performing edit or delete modifications.
  Users need to be aware of the following when using this feature:
  
  API Objects VolumeSnapshot, VolumeSnapshotContent, and VolumeSnapshotClass
  are CRDs, not
  part of the core API.
  VolumeSnapshot support is only available for CSI drivers.
  As part of the deployment process of VolumeSnapshot, the Kubernetes team provides
  a snapshot controller to be deployed into the control plane, and a sidecar helper
  container called csi-snapshotter to be deployed together with the CSI driver.
  The snapshot controller watches VolumeSnapshot and VolumeSnapshotContent objects
  and is responsible for the creation and deletion of VolumeSnapshotContent object.
  The sidecar csi-snapshotter watches VolumeSnapshotContent objects and triggers
  CreateSnapshot and DeleteSnapshot operations against a CSI endpoint.
  There is also a validating webhook server which provides tightened validation on
  snapshot objects. This should be installed by the Kubernetes distros along with
  the snapshot controller and CRDs, not CSI drivers. It should be installed in all
  Kubernetes clusters that has the snapshot feature enabled.
  CSI drivers may or may not have implemented the volume snapshot functionality.
  The CSI drivers that have provided support for volume snapshot will likely use
  the csi-snapshotter. See CSI Driver documentation for details.
  The CRDs and snapshot controller installations are the responsibility of the Kubernetes distribution.
  
  Lifecycle of a volume snapshot and volume snapshot content
  VolumeSnapshotContents are resources in the cluster. VolumeSnapshots are requests
  for those resources. The interaction between VolumeSnapshotContents and VolumeSnapshots
  follow this lifecycle:
  Provisioning Volume Snapshot
  There are two ways snapshots may be provisioned: pre-provisioned or dynamically provisioned.
  Pre-provisioned
  A cluster administrator creates a number of VolumeSnapshotContents. They carry the details
  of the real volume snapshot on the storage system which is available for use by cluster users.
  They exist in the Kubernetes API and are available for consumption.
  Dynamic
  Instead of using a pre-existing snapshot, you can request that a snapshot to be dynamically
  taken
  ```