ZeroDownTime/KubeZero
3
0
Fork 0
Code Issues 1 Pull Requests 29 Packages Projects Releases Wiki Activity

chore(deps): update ghcr.io/k8snetworkplumbingwg/multus-cni docker tag to v4 #18

Open
renovate wants to merge 1 commits from renovate/ghcr.io-k8snetworkplumbingwg-multus-cni-4.x into main
pull from: renovate/ghcr.io-k8snetworkplumbingwg-multus-cni-4.x
merge into: ZeroDownTime:main
Conversation 0 Commits 1 Files Changed 1 +1 -1
renovate commented 2024-11-04 16:07:29 +00:00
Member
Copy Link

This PR contains the following updates:

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

Release Notes

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

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 https://github.com/k8snetworkplumbingwg/network-attachment-definition-client/pull/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: https://github.com/k8snetworkplumbingwg/network-attachment-definition-client/pull/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 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.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [ghcr.io/k8snetworkplumbingwg/multus-cni](https://github.com/k8snetworkplumbingwg/multus-cni) | major | `v3.9.3` -> `v4.1.4` | --- ### Release Notes <details> <summary>k8snetworkplumbingwg/multus-cni (ghcr.io/k8snetworkplumbingwg/multus-cni)</summary> ### [`v4.1.4`](https://github.com/k8snetworkplumbingwg/multus-cni/releases/tag/v4.1.4) [Compare Source](https://github.com/k8snetworkplumbingwg/multus-cni/compare/v4.1.3...v4.1.4) Updates to use go version 1.22 at a minimum, to address concerns in [CVE-2024-24790](https://nvd.nist.gov/vuln/detail/CVE-2024-24790) See related details in [#&#8203;1354](https://github.com/k8snetworkplumbingwg/multus-cni/issues/1354) ### [`v4.1.3`](https://github.com/k8snetworkplumbingwg/multus-cni/releases/tag/v4.1.3) [Compare Source](https://github.com/k8snetworkplumbingwg/multus-cni/compare/v4.1.2...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 https://github.com/k8snetworkplumbingwg/network-attachment-definition-client/pull/73 ### [`v4.1.2`](https://github.com/k8snetworkplumbingwg/multus-cni/releases/tag/v4.1.2) [Compare Source](https://github.com/k8snetworkplumbingwg/multus-cni/compare/v4.1.1...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: https://github.com/k8snetworkplumbingwg/network-attachment-definition-client/pull/72 ### [`v4.1.1`](https://github.com/k8snetworkplumbingwg/multus-cni/releases/tag/v4.1.1) [Compare Source](https://github.com/k8snetworkplumbingwg/multus-cni/compare/v4.1.0...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. ### [`v4.1.0`](https://github.com/k8snetworkplumbingwg/multus-cni/releases/tag/v4.1.0) [Compare Source](https://github.com/k8snetworkplumbingwg/multus-cni/compare/v4.0.2...v4.1.0) 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`](https://github.com/k8snetworkplumbingwg/multus-cni/releases/tag/v4.0.2) [Compare Source](https://github.com/k8snetworkplumbingwg/multus-cni/compare/v4.0.1...v4.0.2) Includes additional CNI DEL error ignored in https://github.com/k8snetworkplumbingwg/multus-cni/pull/1084 ### [`v4.0.1`](https://github.com/k8snetworkplumbingwg/multus-cni/compare/v4.0.0...v4.0.1) [Compare Source](https://github.com/k8snetworkplumbingwg/multus-cni/compare/v4.0.0...v4.0.1) ### [`v4.0.0`](https://github.com/k8snetworkplumbingwg/multus-cni/releases/tag/v4.0.0) [Compare Source](https://github.com/k8snetworkplumbingwg/multus-cni/compare/v3.9.3...v4.0.0) This is the release of Multus 4.0, finally! -- which includes a thick-plugin deployment and architecture. </details> --- ### 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOC4xMjQuMSIsInVwZGF0ZWRJblZlciI6IjM5LjMzLjEiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbInJlbm92YXRlIl19-->
renovate added 1 commit 2024-11-04 16:07:29 +00:00
renovate force-pushed renovate/ghcr.io-k8snetworkplumbingwg-multus-cni-4.x from 2703c2924d to 7e86b3e2ed 2024-12-07 03:02:00 +00:00 Compare
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/ghcr.io-k8snetworkplumbingwg-multus-cni-4.x:renovate/ghcr.io-k8snetworkplumbingwg-multus-cni-4.x
git checkout renovate/ghcr.io-k8snetworkplumbingwg-multus-cni-4.x
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: ZeroDownTime/KubeZero#18
No description provided.
Delete Branch "renovate/ghcr.io-k8snetworkplumbingwg-multus-cni-4.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?