Bump github.com/k8snetworkplumbingwg/network-attachment-definition-client from 1.7.5 to 1.7.7

[dependabot]

Bumps github.com/k8snetworkplumbingwg/network-attachment-definition-client from 1.7.5 to 1.7.7.

Release notes

Sourced from github.com/k8snetworkplumbingwg/network-attachment-definition-client's releases.

1.7.7

This release contains a few fixes described below

Fix IP assignment for plugins without interface index Restores behavior assigning IPs without interface index to the last network status, fixing a regression.

Minor update to net-attach-def_test.go in the pkg/utils package.

Allow multiple IP sources in NetworkSelectionElement Removes restriction so both ipam-claim-reference and IPRequest can be used together for flexible IP management.

Full Changelog: k8snetworkplumbingwg/network-attachment-definition-client@v1.7.6...v1.7.7

v1.7.6

This release fixes a regression affecting CNI plugins that do not specify interfaces in their CNI ADD result.

Previously, IP addresses returned without an associated interface index were not being assigned to any network-status entry. This release restores the prior behavior by assigning such IPs to the last network status (i.e., the last sandboxed interface), ensuring consistent handling across plugins, especially those that omit the interfaces field entirely.

This change is important for compatibility with certain CNI plugins and maintains expected behavior from earlier versions of the net-attach-def library.

Special thanks to @​Brian-McM for identifying the issue and providing the fix!

Commits

• 46fcc41 Merge pull request #80 from qinqon/remove-ip-sources-limitation-upstream
• 372cca2 Remove TooManyIPSources limitation for NetworkSelectionElement
• e12bd55 Merge pull request #77 from Brian-McM/assign-ips-with-no-interface-to-default...
• 77dfd49 Update pkg/utils/net-attach-def_test.go
• 1945b69 Assign IPs that don't have an interface index to the last network status
• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.