push
github
chore: bump github.com/k8snetworkplumbingwg/network-attachment-definition-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/506cfdac9"><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> ... (continued)
3326 of 5509 relevant lines covered (60.37%)
27.7 hits per line