title: How Do I Make A Persistent Volume Accessible to Multiple Kubernetes Pods?
body: <p>I've done quite a bit of research and have yet to find an answer to this. Here's what I'm trying to accomplish:</p>
  
  <ul>
  <li>I have an ELK stack container running in a pod on a k8s cluster in GCE - the cluster also contains a PersistentVolume (format: ext4) and a PersistentVolumeClaim.</li>
  <li>In order to scale the ELK stack to multiple pods/nodes and keep persistent data in ElasticSearch, I either need to have all pods write to the same PV (using the node/index structure of the ES file system), or have some volume logic to scale up/create these PVs/PVCs.</li>
  <li>Currently what happens is if I spin up a second pod on the replication controller, it can't mount the PV.</li>
  </ul>
  
  <p>So I'm wondering if I'm going about this the wrong way, and what is the best way to architect this solution to allow for persistent data in ES when my cluster/nodes autoscale.</p>