<p>I know that PVC can be used as a volume in k8s. I know how to create them and how to use, but I couldn't understand why there are two of them, PV and PVC. </p>

<p>Can someone give me an architectural reason behind PV/PVC distinction? What kind of problem it try to solve (or what historical is behind this)?</p>

<p>Despite their names, they serve two different purposes: an abstraction for storage (PV) and a request for such storage (PVC). Together, they enable a clean separation of concerns (using a figure from our <a href="http://shop.oreilly.com/product/0636920064947.do" rel="noreferrer">Kubernetes Cookbook</a> here to illustrate this):</p>

<p><a href="https://i.stack.imgur.com/tfniF.png" rel="noreferrer"><img src="https://i.stack.imgur.com/tfniF.png" alt="enter image description here"></a></p>

<p>The storage admin focuses on provisioning PVs (ideally <a href="http://shop.oreilly.com/product/0636920064947.do" rel="noreferrer">dynamically</a> through defining storage classes) and the developer uses a PVC to acquire a PV and use it in a pod.</p>
