Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore: bump github.com/k8snetworkplumbingwg/network-attachment-defini…
…tion-client from 1.7.1 to 1.7.3 (#1069) Bumps [github.com/k8snetworkplumbingwg/network-attachment-definition-client](https://github.com/k8snetworkplumbingwg/network-attachment-definition-client) from 1.7.1 to 1.7.3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/k8snetworkplumbingwg/network-attachment-definition-client/releases">github.com/k8snetworkplumbingwg/network-attachment-definition-client's releases</a>.</em></p> <blockquote> <h2>v1.7.3</h2> <p>This release accounts for the sandox interfaces when reporting the interfaces in the network-status annotation; in case the CreateNetworkStatuses clients invoke it with a CNI result featuring non-sandbox interfaces as the first item in the list, this release accounts for that condition.</p> <h2>v1.7.2</h2> <p>When the <code>CreateNetworkStatuses</code> method was created to properly set the network-status annotation when a CNI result includes multiple interfaces in the return, it was found that it when setting the "default" parameter in the network-status, it was setting it to all the returned interfaces to true, which doesn't fit the NPWG net-attach-def specification.</p> <p>This release fixes that issue by using the first interface in the CNI result set to <code>"default": true</code> for the cluster default network and not the following interfaces.</p> <p><em>NOTE</em> Do not use this version, use >= v1.7.3</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/k8snetworkplumbingwg/network-attachment-definition-client/commit/506cfdac925790adf2f56f27740d2e87eaf2c83c"><code>506cfda</code></a> Merge pull request <a href="https://redirect.github.com/k8snetworkplumbingwg/network-attachment-definition-client/issues/71">#71</a> from maiqueb/account-for-sandbox-ifaces-when-choosing-...</li> <li><a href="https://github.com/k8snetworkplumbingwg/network-attachment-definition-client/commit/d8782ff3981835b528f411b0cf1316608749011f"><code>d8782ff</code></a> Accont for non-sandbox interfaces when specifying the default network</li> <li><a href="https://github.com/k8snetworkplumbingwg/network-attachment-definition-client/commit/d23f60f2814d9392f5b11db671a92d3547e9dbba"><code>d23f60f</code></a> Merge pull request <a href="https://redirect.github.com/k8snetworkplumbingwg/network-attachment-definition-client/issues/70">#70</a> from maiqueb/multiple-default-interfaces</li> <li><a href="https://github.com/k8snetworkplumbingwg/network-attachment-definition-client/commit/afe49cd347a7c84f77723e0b6a3c91749414a29b"><code>afe49cd</code></a> Comply with de-facto standar for multiple interfaces single ADD request</li> <li>See full diff in <a href="https://github.com/k8snetworkplumbingwg/network-attachment-definition-client/compare/v1.7.1...v1.7.3">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details>
- Loading branch information
