feat(CSI-249): optimize NFS mounter to use multiple targets

[sergeyberezansky]

TL;DR

Added a new function to determine the node's IP address based on routing to a target host.

What changed?

• Introduced a new function GetNodeIpAddressByRouting in utils.go that determines the node's IP address by creating a UDP connection to a target host.
• Updated the doMount function in nfsmount.go to use the new GetNodeIpAddressByRouting function, falling back to GetNodeIpAddress if it fails.
• Added unit tests for the new GetNodeIpAddressByRouting function in utils_test.go.

How to test?

1. Run the new unit tests in utils_test.go to verify the functionality of GetNodeIpAddressByRouting.
2. Test the NFS mount process with different network configurations to ensure it correctly determines the node's IP address.
3. Verify that the mount process falls back to the original GetNodeIpAddress function if GetNodeIpAddressByRouting fails.

Why make this change?

This change improves the accuracy of determining the node's IP address for NFS mounts, especially in complex network environments. By using routing information to determine the IP address, we can ensure that the correct network interface is used for NFS communications, potentially resolving issues related to multi-homed systems or specific network configurations.

---

feat(deps): implement InterfaceGroup.GetRandomIpAddress()

feat(deps): implement InterfaceGroup.GetRandomIpAddress()

refactor(deps): allow multimount for NFS

refactor(deps): unmount underlying FS straight after publishing volume

[sergeyberezansky]

• #326
• #323
• #322
• #320
• #319
• #318 👈
• #317
• #316
• #314
• #313
• #312
• #311
• #315
• #325
• #299
• #310
• #324
• dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @sergeyberezansky and the rest of your teammates on Graphite

[graphite-app[bot]]

Graphite Automations

"Request reviewers once CI passes" took an action on this PR • (09/05/24)

1 reviewer was added to this PR based on Sergey Berezansky's automation.

[sergeyberezansky]

Merge activity

• Sep 12, 6:10 AM EDT: @sergeyberezansky started a stack merge that includes this pull request via Graphite.
• Sep 12, 7:43 AM EDT: Graphite couldn't merge this pull request because a downstack PR #316 failed to merge.
• Sep 12, 8:43 AM EDT: @sergeyberezansky started a stack merge that includes this pull request via Graphite.
• Sep 12, 8:45 AM EDT: The Graphite merge of this pull request was cancelled.