![]() Make the PVC protection controller robust to cases where a Pod X is deleted, then a Pod Y with the same namespaced name is created and the two events are delivered via a single update notification. Both pods should be processed, because X might be blocking deletion of a PVC which is not referenced by Y. Prior to this commit only the newer pod is processed, which means that it is possible to leak PVCs. Also, add unit tests to reflect the change. |
||
---|---|---|
.. | ||
attachdetach | ||
events | ||
expand | ||
persistentvolume | ||
protectionutil | ||
pvcprotection | ||
pvprotection | ||
scheduling | ||
OWNERS |