Locked NodeExpandVolume by Volume ID

[mdzraf]

What type of PR is this?

/kind feature

What is this PR about? / Why do we need it?

This PR ensures that if NodeExpandVolume is called more than once on the same volume while a previous expand request is in progress, only the current in-flight call succeeds and there are no attempts to perform multiple resizes on the same volume. This is done by locking NodeExpandVolume based on the volume ID.

How was this change tested?

Added a unit test that test for this specific mechanism working on NodeExpandVolume tests. Also tested that expansion happy case works as expected.

Does this PR introduce a user-facing change?

Added Lock To Prevent Multiple Resize Attempts On The Same Volume If An In-flight Resize Request Already Exists.

[k8s-ci-robot]

Hi @mdzraf. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ElijahQuinones]

/ok-to-test

[ConnorJC3]

/lgtm

[torredil]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: torredil

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [torredil]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment