<p>I got a service that needs to scan large files and process them, upload them back to the file server.
My problem is that default available space in a pod is 10G which is not enough.
I have 3 options:</p>
<ol>
<li>use hostFile/emptyDir volume, but this way I can't specify how much space I need, my pods could be scheduled to a node which didn't have enough disk space.</li>
<li>use hostFile persistent volume, but the documents say it is &quot;Single node testing only“</li>
<li>use local persistent volume, but according to the document <code>Dynamic provisioning is not supported yet</code>, I have to manually create pv in each node which seems not acceptable by me, but if there is no other options this will be the only way to go.</li>
</ol>
<p>Is there any other simpler options than <code>local persistent volume</code>?</p>

Nick Allen
<p>Depending on your cloud provider you can mount their block storage options e.g
e.g. Google Cloud Storage, Azure storage by Azure, Elasticblockstore for AWS.
This way you won`t be depended on your node availability for storage. All of them are supported in Kubernetes via plugins as an <a href="https://kubernetes.io/docs/concepts/storage/persistent-volumes/#expanding-persistent-volumes-claims" rel="nofollow noreferrer">expanded persistent volume claims</a>. For example:</p>
<p><strong>gcePersistentDisk</strong></p>
<blockquote>
<p>A <code>gcePersistentDisk</code> volume mounts a Google Compute Engine (GCE)
<a href="https://cloud.google.com/compute/docs/disks" rel="nofollow noreferrer">Persistent Disk</a> into
your Pod. Unlike <code>emptyDir</code>, which is erased when a Pod is removed,
the contents of a PD are preserved and the volume is merely unmounted.
This means that a PD can be pre-populated with data, and that data can
be &quot;handed off&quot; between Pods.T</p>
</blockquote>
<p>This is similar for <a href="https://kubernetes.io/docs/concepts/storage/volumes/#awselasticblockstore" rel="nofollow noreferrer">awsElasticBlockStore</a> or <a href="https://kubernetes.io/docs/concepts/storage/volumes/#azuredisk" rel="nofollow noreferrer">azureDisk</a></p>
<hr />
<p>If you want to use AWS S3 there is an <a href="https://operatorhub.io/operator/awss3-operator-registry" rel="nofollow noreferrer">S3 Operator</a> which you may find interesting.</p>
<blockquote>
<p>AWS S3 Operator will deploy the AWS S3 Provisioner which will
dynamically or statically provision AWS S3 Bucket storage and access.</p>
</blockquote>
