<p>I have a pod that needs to save data persistently to a place outside the pod. I think a persistentVolume is a good idea for that. The pod called writerPod needs ReadWrite-access to that volume.</p>
<p>Multiple other Pods (I'm calling them readingPods) need to read the files that writerPod saved.</p>
<p>Is it possible to have two persistentVolumeClaims (PVC) (that differ only in the accessMode ReadWriteOnce and ReadOnlyMany) that both bind the same PersistentVolume?</p>

<p>PVC can have more than one accessMode configured (both ReadOnlyMany and ReadWriteOnce):</p>
<pre><code>  accessModes:
  - ReadWriteOnce
  - ReadOnlyMany
</code></pre>
<p>However, as the names imply, you can mount the disk to many pods in ReadOnlyMany (AKA <code>ROX</code>) but only one pod at a time can use that disk in ReadWriteOnce mode (AKA <code>RWO</code>).</p>
<p>If your readingPods should be up only after your writerPod has written its data - you can use the same PVC, just make sure your mounting the PVC with the readOnly flag set to true, for example:</p>
<pre><code>volumes:
- name: test-volume
  persistentVolumeClaim:
    claimName: my-pvc
    readOnly: true
</code></pre>
<p>If you're using a Cloud provider that supports the ReadWriteMany access mode (Unfortunately, Google is not one of them right now) it will of-course suit you in all scenarios. Check the <a href="https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes" rel="nofollow noreferrer">official documentation</a> to check the supported modes on each platform.</p>
