Change node-level idempotency to volume-target #360
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Is this a bug fix or adding new feature?
bug fix
What is this PR about? / Why do we need it?
This PR changes the behavior of Node-level idempotency for the CSI Driver. Currently, the node-level operations are idempotent using
volumeID
. This behavior prevents two pods from mounting the same volume in parallel. When one pod is stuck pending/terminating (mounting/unmounting), this prevents all other pods from mounting or unmounting the volume. Since each pod has a unique target:volume, we use the target in the inflight key to ensure that idempotency is pod-volume-level, not node-volume-level.What testing is done?