Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update net-attach-def client library to 1.7.5 for cri-o functionality #1345

Merged
merged 1 commit into from
Oct 15, 2024
Merged

Update net-attach-def client library to 1.7.5 for cri-o functionality #1345

merged 1 commit into from
Oct 15, 2024

Commits on Oct 15, 2024

  1. Update net-attach-def client library to 1.7.5 for cri-o functionality 

    From the release notes:

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

See also:
https://github.com/k8snetworkplumbingwg/network-attachment-definition-client/releases/tag/v1.7.5
k8snetworkplumbingwg/network-attachment-definition-client#73
    @dougbtv
    dougbtv committed Oct 15, 2024
    Configuration menu
    Copy the full SHA
    ecf5854 View commit details
    Browse the repository at this point in the history