Update ghcr.io/k8snetworkplumbingwg/multus-cni Docker tag to v4

[renovate]

This PR contains the following updates:

Package	Update	Change
ghcr.io/k8snetworkplumbingwg/multus-cni	major	v3.8.1 → v4.2.3

---

Release Notes

k8snetworkplumbingwg/multus-cni (ghcr.io/k8snetworkplumbingwg/multus-cni)

v4.2.3

Compare Source

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: k8snetworkplumbingwg/multus-cni@v4.2.2...v4.2.3

v4.2.2

Compare Source

• 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

Compare Source

• 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

Compare Source

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

Compare Source

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

Compare Source

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

Compare Source

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

Compare Source

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.

v4.1.0

Compare Source

Primarily a maintenance release after some time, but, does include some notable features:

• Initial implementation for DRA (dynamic resource allocation)
• Updated net-attach-def-client library with fixes for multiple interfaces in CNI results
• Includes fixes for parity with configuration options from Multus 3.x
• Improved API handling using informers

v4.0.2

Compare Source

Includes additional CNI DEL error ignored in #​1084

v4.0.1

Compare Source

v4.0.0

Compare Source

This is the release of Multus 4.0, finally! -- which includes a thick-plugin deployment and architecture.

v3.9.3

Compare Source

Exposes the device-representor in device-info-spec.

v3.9.2

Compare Source

Fixes image tag ambiguity / problems with image labeled :thick

v3.9.1: Multus v3.9.1

This is the last v3 minor tag prior to merging changes for Multus 4.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 was generated by Mend Renovate. View the repository job log.