v4.3.0

DeviceID ordering is now deterministic (alphabetically sorted). 
CNIs relying on specific device positions may see different assignments.

What's Changed

• ci: update trivy-action to v0.35.0 to fix image scanning failure by @bpickard22 in #1484
• Sort DeviceIDs in GetPodResourceMap for deterministic ordering by @cathy-zhou in #1481
• Bump multus-cni to Kube 1.35 and Go to 1.25 by @yingwang-0320 in #1487
• k8sclient: use ServerVersion instead of pod list for kubeconfig validation by @pliurh in #1478
• Fix thick plugin STATUS and GC handling for plugin-level commands by @tsorya in #1490
• Add "nad" as shortName by @dgsponer in #1476
• e2e: Use fully qualified image name for images by @RamLavi in #1472
• Bump google.golang.org/grpc from 1.73.0 to 1.79.3 by @dependabot[bot] in #1491
• Pin GH Actions to commit sha by @thomasferrandiz in #1494
• Add optional pprof endpoint support to multus-daemon by @bpickard22 in #1509
• Add connection limit for thick daemon. by @hrntknr in #1510

New Contributors

• @bpickard22 made their first contribution in #1484
• @tsorya made their first contribution in #1490
• @dgsponer made their first contribution in #1476
• @RamLavi made their first contribution in #1472
• @hrntknr made their first contribution in #1510

Full Changelog: v4.2.4...v4.3.0

v4.2.4

What's Changed

• Adds support for CNI STATUS + other fixes for CNI Spec 1.1.0 by @trozet in #1470
• Bump Multus to Kube 1.34 by @yingwang-0320 in #1443
• Bump github.com/containernetworking/plugins from 1.7.1 to 1.9.0 by @dependabot[bot] in #1464
• chore: update Go version to 1.24.11 by @rollandf in #1467
• Fix typo: cilium spelling by @linuzctl in #1465

New Contributors

• @yingwang-0320 made their first contribution in #1443
• @linuzctl made their first contribution in #1465

Full Changelog: v4.2.3...v4.2.4

v4.2.3

What's Changed

• Bump to go 1.24 by @thomasferrandiz in #1451
• Fix node reboot issue by using install_multus bin to update cni file by @Untersander in #1445

New Contributors

• @Untersander made their first contribution in #1445

Full Changelog: v4.2.2...v4.2.3

v4.2.2

• Bump to go version 1.23
• Bump to k8s version 1.32.5
• Add simple Makefile
• Fix missing config on startup error
• Add support for CNI Spec v1.1.0
• Deprecate legacy CNI Spec versions

v4.2.1

• Thick client: mount multus-conf-dir
• Subdirectory CNI chain loading e2e tests
• Functionality for Aux CNI Chain using subdirectory based CNI configuration loading.
• Use cross-compilation for thick plugin build
• Add trivy vulnerability scanner in build step
• Properly structure empty CNI result return
• Bumps to libcni v1.3.0

v4.2.0

This release is focused on reliability and compatibility updates:

• Supports CNI spec v1.2.0
• Updated network-attachment-definition-client to v1.7.6 (thanks @Brian-McM! for the fix)
• Handles "pod not found" during CNI ADD gracefully
  • And tolerates network-status annotation failures on fast-deleted pods (when they're not found)
• Adds context + better timeout handling for API server calls
• Avoids stale cache issues with live pod lookups
• (And there's fixes for e2e config and runtimeConfig API versions)

v4.1.4

Updates to use go version 1.22 at a minimum, to address concerns in CVE-2024-24790

See related details in #1354

v4.1.3

Updates net-attach-def client library to 1.7.5

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

v4.1.2

Updates net-attach-def client for improvements backwards compatibility for network-status in latest updates to the client library, especially related to Calico.

See also: k8snetworkplumbingwg/network-attachment-definition-client#72

v4.1.1

Updates net-attach-def client to v1.7.3 to account for fixes relative to the Network Plumbing Working Group specification, especially how CNI results are handled when the CNI result contains more than one container-side interface in the return.