<p>Assume currently I have 2 <code>PVC</code>s with <code>ReadWriteOnce</code>, claimed by <code>Pod #1</code> and <code>Pod #2</code> respectively. Both are running on <code>Node #1</code>.</p>

<p>Next, <code>Pod #2</code> is updated with the newer Docker image. However, at the same time <code>Pod #3</code> is run and allocated to <code>Node #1</code>. Since <code>Node #1</code> is now full, <code>Pod #2</code> could only be allocated by Kubernetes to <code>Node #2</code>.</p>

<p>Since AWS EBS and Google PersistentDisk could only be mounted on single Node, would <code>Pod #2</code> become unable to connect to the-previously-claimed <code>PVC</code>? </p>

<p>If yes, how to avoid having this issue?</p>

<p>Yes, that is the downside of pv/pvc with the current storage deliveries of AWS and GCE.</p>

<p>To avoid this, you would have to use a different storage infrastructure which does not have this limitation. Possibilities are CEPH, Gluster, scaleIO (and others). These solutions abstract the storage away from the disks and provide a storage layer which is not node dependent anymore.</p>
