Can ReadWriteOnce PVC be rejected by AWS EBS/GCP PersistentDisk upon Pod Rescheduling?

Viewed 99

Assume currently I have 2 PVCs with ReadWriteOnce, claimed by Pod #1 and Pod #2 respectively. Both are running on Node #1.

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

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

If yes, how to avoid having this issue?

2 Answers
Related