<p>I have a 3 node coros kubernetes cluster up and running.</p>

<p>I want to use persitentvolumes(pv) from a standalone NFS Server.</p>

<p>nfs.yaml</p>

<pre><code>apiVersion: v1
kind: PersistentVolume
metadata:
  name: kube1
spec:
  capacity:
    storage: 9.5G
  accessModes:
    - ReadWriteMany
  nfs:
    path: /mnt/nfs/kube1
    server: 10.3.0.3
</code></pre>

<p>claim.yaml</p>

<pre><code>kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: pvc2-1
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 1G
</code></pre>

<p><code>kubecfg get pv</code></p>

<p><code>kube1     &lt;none&gt;    9500M      RWX           Released   default/pvc2-1</code></p>

<p><code>kubecfg get pvc</code></p>

<p><code>pvc2-1    &lt;none&gt;    Bound     kube1     9500M      RWX</code></p>

<p>So why is the pvc created with the full capacity of pv? As I assumed that pvc is just a part of pv, otherwise it's pretty useless.</p>

<p>Regards</p>

<p>cdpb</p>

<p>As far as I've seen, that's the way it should work. The claim is for the entire volume. The part that confused me at first as well, was the resources.requests.storage value is only a minimum value that claim requires. I use this with Ceph, and when Pods bind to the block device, they take the whole volume.</p>
