Skip to content

Update module github.com/k8snetworkplumbingwg/network-attachment-definition-client to v1.7.5 - #1145

Merged
openshift-merge-bot[bot] merged 1 commit into
mainfrom
renovate/network-attachment-definition-client
Oct 21, 2024
Merged

Update module github.com/k8snetworkplumbingwg/network-attachment-definition-client to v1.7.5#1145
openshift-merge-bot[bot] merged 1 commit into
mainfrom
renovate/network-attachment-definition-client

Conversation

@openstack-k8s-ci-robot

@openstack-k8s-ci-robot openstack-k8s-ci-robot commented Oct 19, 2024

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
github.com/k8snetworkplumbingwg/network-attachment-definition-client indirect patch v1.7.4 -> v1.7.5

Release Notes

k8snetworkplumbingwg/network-attachment-definition-client (github.com/k8snetworkplumbingwg/network-attachment-definition-client)

v1.7.5

Compare Source

This release contains a fix related to the determination of the default interface, e.g. setting the default parameter to true in the network-status annotation based on the presence of a gateway in the CNI ADD success result ips.gateway and makes the determination of the default based on the first interface that has an associated value of gateway (using the interface index in the ips element in the CNI ADD success result).

This provides flexibility especially in CRI-O which uses the first interface and IP addresses for the pod.IP in Kubernetes, therefore. Containerd functionality is unchanged in that it uses the value for the IP addresses specifically

It'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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@openshift-ci
openshift-ci Bot requested review from bshephar and rebtoor October 19, 2024 04:58
@openstack-k8s-ci-robot
openstack-k8s-ci-robot force-pushed the renovate/network-attachment-definition-client branch from 892ec9d to 837d2ec Compare October 21, 2024 08:03
@openshift-ci

openshift-ci Bot commented Oct 21, 2024

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fao89, openstack-k8s-ci-robot

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot
openshift-merge-bot Bot merged commit c43c0f2 into main Oct 21, 2024
@openstack-k8s-ci-robot
openstack-k8s-ci-robot deleted the renovate/network-attachment-definition-client branch October 21, 2024 13:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants