instruction: Configure Kubernetes persistent volume storage with subPath
output: ```dockerfile
  from the host node's filesystem
  into your Pod. This is not something that most Pods will need, but it offers a
  powerful escape hatch for some applications.
  
  Warning: Using the hostPath volume type presents many security risks.
  If you can avoid using a hostPath volume, you should. For example,
  define a local PersistentVolume, and use that instead.
  If you are restricting access to specific directories on the node using
  admission-time validation, that restriction is only effective when you
  additionally require that any mounts of that hostPath volume are
  read only. If you allow a read-write mount of any host path by an
  untrusted Pod, the containers in that Pod may be able to subvert the
  read-write host mount.
  
  Take care when using hostPath volumes, whether these are mounted as read-only
  or as read-write, because:
  
  Access to the host filesystem can expose privileged system credentials (such as for the kubelet) or privileged APIs
  (such as the container runtime socket), that can be used for container escape or to attack other
  parts of the cluster.
  Pods with identical configuration (such as created
  ```