openstack-k8s-operators / openstack-operator

Meta Operator for OpenStack
https://openstack-k8s-operators.github.io/openstack-operator/
Apache License 2.0
27 stars 76 forks source link

Update module github.com/k8snetworkplumbingwg/network-attachment-definition-client to v1.7.3 #1110

Open openstack-k8s-ci-robot opened 2 days ago

openstack-k8s-ci-robot commented 2 days ago

This PR contains the following updates:

Package Type Update Change
github.com/k8snetworkplumbingwg/network-attachment-definition-client indirect minor v1.4.0 -> v1.7.3

Release Notes

k8snetworkplumbingwg/network-attachment-definition-client (github.com/k8snetworkplumbingwg/network-attachment-definition-client) ### [`v1.7.3`](https://redirect.github.com/k8snetworkplumbingwg/network-attachment-definition-client/releases/tag/v1.7.3) [Compare Source](https://redirect.github.com/k8snetworkplumbingwg/network-attachment-definition-client/compare/v1.7.2...v1.7.3) 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. ### [`v1.7.2`](https://redirect.github.com/k8snetworkplumbingwg/network-attachment-definition-client/releases/tag/v1.7.2) [Compare Source](https://redirect.github.com/k8snetworkplumbingwg/network-attachment-definition-client/compare/v1.7.1...v1.7.2) When the `CreateNetworkStatuses` 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. This release fixes that issue by using the first interface in the CNI result set to `"default": true` for the cluster default network and not the following interfaces. *NOTE* Do not use this version, use >= v1.7.3 ### [`v1.7.1`](https://redirect.github.com/k8snetworkplumbingwg/network-attachment-definition-client/releases/tag/v1.7.1) [Compare Source](https://redirect.github.com/k8snetworkplumbingwg/network-attachment-definition-client/compare/v1.7.0...v1.7.1) Adds the `CreateNetworkStatuses` method to properly set the `network-status` annotation when a CNI result includes multiple interfaces in the return. For details of the before/after, see this gist: https://gist.github.com/dougbtv/1eb8ac2d61d494b56d65a6b236a86e61 For the related suggested update to the NPWG net-attach-def specification (for clarity only), see this proposal @​ https://docs.google.com/document/d/1DUTV-o6E6zlRTKZkxeDhAeyGrmq03qPgPbU580Rm7-g/edit ### [`v1.7.0`](https://redirect.github.com/k8snetworkplumbingwg/network-attachment-definition-client/releases/tag/v1.7.0) [Compare Source](https://redirect.github.com/k8snetworkplumbingwg/network-attachment-definition-client/compare/v1.6.0...v1.7.0) Adds MTU to network-status ### [`v1.6.0`](https://redirect.github.com/k8snetworkplumbingwg/network-attachment-definition-client/releases/tag/v1.6.0) [Compare Source](https://redirect.github.com/k8snetworkplumbingwg/network-attachment-definition-client/compare/v1.5.0...v1.6.0) Adds IPAMClaimReference to network-selection-elements ### [`v1.5.0`](https://redirect.github.com/k8snetworkplumbingwg/network-attachment-definition-client/releases/tag/v1.5.0) [Compare Source](https://redirect.github.com/k8snetworkplumbingwg/network-attachment-definition-client/compare/v1.4.0...v1.5.0) #### What's Changed - Add NOTICE file for Apache license 2.0 by [@​s1061123](https://redirect.github.com/s1061123) in [https://github.com/k8snetworkplumbingwg/network-attachment-definition-client/pull/53](https://redirect.github.com/k8snetworkplumbingwg/network-attachment-definition-client/pull/53) - Update venodrs by [@​s1061123](https://redirect.github.com/s1061123) in [https://github.com/k8snetworkplumbingwg/network-attachment-definition-client/pull/62](https://redirect.github.com/k8snetworkplumbingwg/network-attachment-definition-client/pull/62) #### New Contributors **Full Changelog**: https://github.com/k8snetworkplumbingwg/network-attachment-definition-client/compare/v1.4.0...v1.5.0

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone America/New_York, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.



This PR has been generated by Renovate Bot.

openshift-ci[bot] commented 2 days ago

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openstack-k8s-ci-robot Once this PR has been reviewed and has the lgtm label, please assign rabi for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files: - **[OWNERS](https://github.com/openstack-k8s-operators/openstack-operator/blob/main/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
openshift-ci[bot] commented 2 days ago

@openstack-k8s-ci-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/openstack-operator-build-deploy-kuttl 70d3b254687f14b68247e415b9564f0b2fa0146c link true /test openstack-operator-build-deploy-kuttl

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
softwarefactory-project-zuul[bot] commented 2 days ago

Build failed (check pipeline). Post recheck (without leading slash) to rerun all jobs. Make sure the failure cause has been resolved before you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/bfb51ee2961d403b9fab3141952f4f0f

:heavy_check_mark: openstack-k8s-operators-content-provider SUCCESS in 2h 00m 59s :heavy_check_mark: podified-multinode-edpm-deployment-crc SUCCESS in 1h 15m 52s :heavy_check_mark: cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 32m 17s :x: adoption-standalone-to-crc-ceph-provider FAILURE in 1h 40m 40s :heavy_check_mark: openstack-operator-tempest-multinode SUCCESS in 1h 48m 18s