-
Notifications
You must be signed in to change notification settings - Fork 31
Update module github.com/k8snetworkplumbingwg/network-attachment-definition-client to v1.7.5 #411
base: main
Are you sure you want to change the base?
Update module github.com/k8snetworkplumbingwg/network-attachment-definition-client to v1.7.5 #411
Conversation
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: openstack-k8s-ci-robot The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/ee95f304651d49edbe017f808bbd5549 ❌ openstack-k8s-operators-content-provider FAILURE in 5m 25s |
925358e to
4f95e13
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/effc33cc179e408da4c287928a7173e2 ❌ openstack-k8s-operators-content-provider FAILURE in 5m 47s |
4f95e13 to
79bfb92
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/644596e22f504ca2a65a55c3b2be6d1d ❌ openstack-k8s-operators-content-provider FAILURE in 5m 23s |
79bfb92 to
6c28d10
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/fcd96ee775f5464393f772d105b173a6 ❌ openstack-k8s-operators-content-provider FAILURE in 5m 31s |
…nition-client to v1.7.5
6c28d10 to
eb5e748
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/6f9b64e5ff2445d5a2079afc3d48642c ❌ openstack-k8s-operators-content-provider FAILURE in 5m 36s |
|
@openstack-k8s-ci-robot: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
This PR contains the following updates:
v1.4.0->v1.7.5Release Notes
k8snetworkplumbingwg/network-attachment-definition-client (github.com/k8snetworkplumbingwg/network-attachment-definition-client)
v1.7.5Compare Source
This release contains a fix related to the determination of the default interface, e.g. setting the
defaultparameter totruein thenetwork-statusannotation based on the presence of a gateway in the CNI ADD success resultips.gatewayand makes the determination of the default based on the first interface that has an associated value of gateway (using the interface index in theipselement in the CNI ADD success result).This provides flexibility especially in CRI-O which uses the first interface and IP addresses for the
pod.IPin Kubernetes, therefore. Containerd functionality is unchanged in that it uses the value for the IP addresses specificallyIt's worth noting that CNI ADD success results which do not contain any interfaces will be discarded in this determination of the default, therefore it's recommended to set one with an associated gateway if aiming to have it be noted as the default.
v1.7.4Compare Source
This release accounts for CNI plugins which do not use the sandbox field in results when calculating the network-status annotation, doing so for backwards compatibility for plugins which choose to not use this field (such as Calico)
v1.7.3Compare Source
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.2Compare Source
When the
CreateNetworkStatusesmethod 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": truefor the cluster default network and not the following interfaces.NOTE Do not use this version, use >= v1.7.3
v1.7.1Compare Source
Adds the
CreateNetworkStatusesmethod to properly set thenetwork-statusannotation 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.0Compare Source
Adds MTU to network-status
v1.6.0Compare Source
Adds IPAMClaimReference to network-selection-elements
v1.5.0Compare Source
What's Changed
New Contributors
Full Changelog: k8snetworkplumbingwg/network-attachment-definition-client@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.