feat(container)!: Update image ghcr.io/k8snetworkplumbingwg/multus-cni ( v3.9.3 → v4.1.1 )

[samip5-bot[bot]]

This PR contains the following updates:

Package	Update	Change
ghcr.io/k8snetworkplumbingwg/multus-cni	major	v3.9.3 -> v4.1.1

---

Release Notes

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

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 https://github.com/k8snetworkplumbingwg/multus-cni/pull/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.

---

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 has been generated by Renovate Bot.

[github-advanced-security[bot]]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.