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

fix(container): update image ghcr.io/k8snetworkplumbingwg/multus-cni ( v4.1.2 → v4.1.3 ) #1123

Merged

Conversation

kireque-bot[bot]
Copy link
Contributor

@kireque-bot kireque-bot bot commented Oct 15, 2024

This PR contains the following updates:

Package Update Change
ghcr.io/k8snetworkplumbingwg/multus-cni patch v4.1.2-thick -> v4.1.3-thick

Release Notes

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

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


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.

…( v4.1.2 → v4.1.3 )

| datasource | package                                 | from   | to     |
| ---------- | --------------------------------------- | ------ | ------ |
| docker     | ghcr.io/k8snetworkplumbingwg/multus-cni | v4.1.2 | v4.1.3 |
@kireque-bot kireque-bot bot added renovate/container Issue relates to a Renovate container update type/patch Issue relates to a patch version bump area/kubernetes Issue relates to Kubernetes cluster/main Issue relates to the "main" cluster labels Oct 15, 2024
@kireque-bot
Copy link
Contributor Author

kireque-bot bot commented Oct 15, 2024

--- HelmRelease: network/multus DaemonSet: network/multus

+++ HelmRelease: network/multus DaemonSet: network/multus

@@ -54,13 +54,13 @@

         - |
           set -x
           cp -f /usr/src/multus-cni/bin/multus-shim /host/opt/cni/bin/multus-shim
         command:
         - /bin/sh
         - -c
-        image: ghcr.io/k8snetworkplumbingwg/multus-cni:v4.1.2-thick
+        image: ghcr.io/k8snetworkplumbingwg/multus-cni:v4.1.3-thick
         name: multus-shim-installer
         resources:
           requests:
             cpu: 10m
             memory: 15Mi
         securityContext:
@@ -75,13 +75,13 @@

       containers:
       - env:
         - name: MULTUS_NODE_NAME
           valueFrom:
             fieldRef:
               fieldPath: spec.nodeName
-        image: ghcr.io/k8snetworkplumbingwg/multus-cni:v4.1.2-thick
+        image: ghcr.io/k8snetworkplumbingwg/multus-cni:v4.1.3-thick
         name: multus-daemon
         resources:
           limits:
             memory: 512Mi
           requests:
             cpu: 5m

@kireque-bot
Copy link
Contributor Author

kireque-bot bot commented Oct 15, 2024

--- kubernetes/main/apps/network/multus/app Kustomization: flux-system/multus HelmRelease: network/multus

+++ kubernetes/main/apps/network/multus/app Kustomization: flux-system/multus HelmRelease: network/multus

@@ -46,13 +46,13 @@

               MULTUS_NODE_NAME:
                 valueFrom:
                   fieldRef:
                     fieldPath: spec.nodeName
             image:
               repository: ghcr.io/k8snetworkplumbingwg/multus-cni
-              tag: v4.1.2-thick
+              tag: v4.1.3-thick
             resources:
               limits:
                 memory: 512Mi
               requests:
                 cpu: 5m
                 memory: 96Mi
@@ -79,13 +79,13 @@

               cp -f /usr/src/multus-cni/bin/multus-shim /host/opt/cni/bin/multus-shim
             command:
             - /bin/sh
             - -c
             image:
               repository: ghcr.io/k8snetworkplumbingwg/multus-cni
-              tag: v4.1.2-thick
+              tag: v4.1.3-thick
             resources:
               requests:
                 cpu: 10m
                 memory: 15Mi
             securityContext:
               capabilities:

@kireque kireque merged commit d7f9092 into main Oct 17, 2024
19 checks passed
@kireque kireque deleted the renovate/main-ghcr.io-k8snetworkplumbingwg-multus-cni-4.x branch October 17, 2024 18:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/kubernetes Issue relates to Kubernetes cluster/main Issue relates to the "main" cluster renovate/container Issue relates to a Renovate container update type/patch Issue relates to a patch version bump
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant