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.

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

feat(container): update image ghcr.io/k8snetworkplumbingwg/multus-cni ( v4.0.2 → v4.1.4 ) #2948

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 7, 2024

This PR contains the following updates:

Package Update Change
ghcr.io/k8snetworkplumbingwg/multus-cni minor v4.0.2 -> v4.1.4

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


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

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.

@renovate renovate bot requested a review from anthr76 as a code owner August 7, 2024 19:20
@renovate renovate bot changed the title feat(container): update image ghcr.io/k8snetworkplumbingwg/multus-cni ( v4.0.2 → v4.1.0 ) feat(container): update image ghcr.io/k8snetworkplumbingwg/multus-cni ( v4.0.2 → v4.1.1 ) Sep 16, 2024
@renovate renovate bot force-pushed the renovate/ghcr.io-k8snetworkplumbingwg-multus-cni-4.x branch from fbed263 to 3667c18 Compare September 16, 2024 14:23
@renovate renovate bot changed the title feat(container): update image ghcr.io/k8snetworkplumbingwg/multus-cni ( v4.0.2 → v4.1.1 ) feat(container): update image ghcr.io/k8snetworkplumbingwg/multus-cni ( v4.0.2 → v4.1.2 ) Oct 7, 2024
@renovate renovate bot force-pushed the renovate/ghcr.io-k8snetworkplumbingwg-multus-cni-4.x branch from 3667c18 to 77f844e Compare October 7, 2024 16:23
@renovate renovate bot force-pushed the renovate/ghcr.io-k8snetworkplumbingwg-multus-cni-4.x branch from 77f844e to 523e277 Compare October 15, 2024 18:49
@renovate renovate bot changed the title feat(container): update image ghcr.io/k8snetworkplumbingwg/multus-cni ( v4.0.2 → v4.1.2 ) feat(container): update image ghcr.io/k8snetworkplumbingwg/multus-cni ( v4.0.2 → v4.1.3 ) Oct 15, 2024
… ( v4.0.2 → v4.1.4 )

| datasource | package                                 | from   | to     |
| ---------- | --------------------------------------- | ------ | ------ |
| docker     | ghcr.io/k8snetworkplumbingwg/multus-cni | v4.0.2 | v4.1.4 |


Signed-off-by: Anthony Rabbito <[email protected]>
@renovate renovate bot changed the title feat(container): update image ghcr.io/k8snetworkplumbingwg/multus-cni ( v4.0.2 → v4.1.3 ) feat(container): update image ghcr.io/k8snetworkplumbingwg/multus-cni ( v4.0.2 → v4.1.4 ) Dec 7, 2024
@renovate renovate bot force-pushed the renovate/ghcr.io-k8snetworkplumbingwg-multus-cni-4.x branch from 523e277 to fa07250 Compare December 7, 2024 01:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants