<p>A question that I can’t seem to find a good answer to and am so confused as to what should be an easy answer. I guess you can say I can't see the forest for the trees.</p>
<p>I have N Pods that need access to the same shared FILE SYSTEM (contains 20Gig of pdfs, HTML) only read. I don’t want to copy it to each Pod and create a Volume in Docker. How should I handle this? I don’t see this as a Stateful App where each pod gets its own changed data.</p>
<ul>
<li><p>Node-0</p>
<ul>
<li>Pod-0
<ul>
<li>Java-app  - NEED READ ACCESS TO SHARED FILE SYSTEM</li>
</ul>
</li>
</ul>
</li>
<li><p>Node-1</p>
<ul>
<li>Pod-1
<ul>
<li>Java-app  - NEED READ ACCESS TO SHARED FILE SYSTEM</li>
</ul>
</li>
</ul>
</li>
<li><p>Node-2</p>
<ul>
<li>Pod-2
<ul>
<li>Java-app  - NEED READ ACCESS TO SHARED FILE SYSTEM</li>
</ul>
</li>
</ul>
</li>
</ul>

user3008410
<p>The persistent volume <a href="https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes" rel="nofollow noreferrer">access mode</a> is called <code>ReadOnlyMany</code>.  Not all volume plugins or CSI drivers support this mode (the <a href="https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes" rel="nofollow noreferrer">linked docco</a> maintains a table for support).</p>
<p>If you are hosting on EKS/AKS/GKE they all provide services based on file shares that can do it. Elsewhere you can use an NFS server.</p>
