<p>In Kubernetes, more specifically GKE, I created a Filestore volume, with the minimum of 1TB.</p>
<p>I created then a Persistent Volume Claim of 20gb.</p>
<p>What happens, if for another service I create another 20gb PVC ?</p>
<p>Specifically, how does this kind of storage work if you want to share the disk space between pods but having different data? Does Google make &quot;batches&quot; of X gb requested and this space is reserved in the disk?</p>

<p>There is a one-to-one mapping between a PVC and a PV, so you cannot create multiple PVCs pointing to the same PV.</p>
<p>But there are two possible ways you can share the underlying Filestore file share across multiple pods.</p>
<ol>
<li><p>You can share a single PVC across multiple pods.  So you could create a single PVC with the total amount of storage you want across all your pods (or just set it to size of the Filestore instance).  You would then mount the same PVC on all of your pods.  To ensure that you don't have any data collision, each pod should write to it's own directory within the PVC.  This will definitely work, but it won't limit or report the storage used by an individual pod.</p>
</li>
<li><p>You can create multiple PVs backed by the same Filestore instance.  When you create each PV, specify the storage size for each PV.  Then create PVCs for each pod.  I believe that you'd still want to make sure that each pod writes to a unique directory.</p>
</li>
</ol>
<p>Lastly, unless you have a specific reason for using Filestore instances, consider using dynamic provisioning with GCE PDs.</p>
