You should be able to set pvc.spec.volumeName to the name of the volume you
want to bind.
On Thu, Oct 13, 2016 at 10:59 PM, Lionel Orellana
wrote:
> In my limited experimentation I had problems with NFS PVs getting wiped
> out even though the policy was set to Retain. In fact I ended up in this
Awesome, thanks for the answers!
On Thu, Oct 13, 2016 at 3:59 PM, Lionel Orellana wrote:
> In my limited experimentation I had problems with NFS PVs getting wiped
> out even though the policy was set to Retain. In fact I ended up in this
> situation where if I created a file in the NFS volume it
In my limited experimentation I had problems with NFS PVs getting wiped out
even though the policy was set to Retain. In fact I ended up in this
situation where if I created a file in the NFS volume it was deleted in
front of my eyes in a few seconds. Obviously I did something very wrong
with the P
NFS mounts can be mounted directly into pods without being PVs like this:
volumes:
name: shared
nfs:
server:
path:
If you are using NFS PVs, then the persistentVolumeReclaimPolicy
determines if the data is wiped when the PVC is released. The default
value is "Retain". It will not
If I create a persistent volume claim using an NFS share that has existing
data, will the data be wipded? Same thing with creating the persistent
volume. Will the existing data be deleted. I want to make existing data
accessible to multiple pods/containers in an NFS share. If I make a
persistent vo
