<p>I currently have a single-node Kubernetes instance running on a VM. The disk attached to this VM is 100GB, but 'df -h' shows that the / partition only has 88GB available (other stuff is used for OS overhead etc...)</p>
<p>I have a kubernetes manifest that creates a 100GB local Persistent Volume.
I also have a pod creating a 100GB Persistent Volume Claim.</p>
<p>Both of these deploy and come up normally even though the entire VM does not even have 100GB available.</p>
<p>To make things even more complicated, the VM is thin provisioned, and only using 20 GB on the actual disk right now...</p>
<p>HOW IS THIS WORKING !?!?</p>

Ian Campbell
<p>The local provisioner does no size checks, nor is the size enforced anyway. The final &quot;volume&quot; is just a bind mount like with hostPath. The main reason <code>local</code> PVs exist is because hostPath isn't something the scheduler understands so in a multi-node scenario it won't restrict topology.</p>
