Update module github.com/k8snetworkplumbingwg/network-attachment-definition-client to v1.7.5 #448
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nition-client to v1.7.5
bshephar
approved these changes
Oct 20, 2024
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bshephar, openstack-k8s-ci-robot The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openstack-k8s-ci-robot
deleted the
renovate/network-attachment-definition-client
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.7.4->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.
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.