adapt push-helm-artifact tool to handle duplicate Helm charts (rke2-multus)
We have the following issue today:
push-helm-artifactjob is detecting inconsistencies between the OCI artifact that we build forrke2-multus:v4.3.102some time ago, and the one currently fetched withhelm pull ...(example error here)- the context of why the content is different is specific to how the RKE2 team handled a split of the multus chart in multus+multus-crd (details here and here)
- the practical situation, today is that the
https://rke2-charts.rancher.ioHelm repoindex.yamlhas two items formultusv4.3.102
curl -sSL https://rke2-charts.rancher.io/index.yaml | yq '[.entries[][] | select(.name == "rke2-multus" and .version == "v4.3.102")]'
- apiVersion: v2
appVersion: 4.3.1
created: "2026-11-10T22:26:20.78689657Z"
dependencies:
- condition: rke2-whereabouts.enabled
name: rke2-whereabouts
repository: file://./charts/rke2-whereabouts
description: Multus Helm chart for Kubernetes
digest: c069cd80a9a7c36fe9c6c9039af9478c6c5ddbcba656d27a6a2ea07503264cf9
home: https://github.com/k8snetworkplumbingwg/multus-cni
icon: https://raw.githubusercontent.com/k8snetworkplumbingwg/multus-cni/master/doc/images/Multus.png
maintainers:
- email: charts@rancher.com
name: Rancher Labs
name: rke2-multus
sources:
- https://github.com/intel/multus-cni
type: application
urls:
- assets/rke2-multus-1.34-1.36/rke2-multus-v4.3.102.tgz
version: v4.3.102
- apiVersion: v1
appVersion: 4.3.1
created: "2026-09-23T00:17:59.346469838Z"
dependencies:
- condition: rke2-whereabouts.enabled
name: rke2-whereabouts
repository: file://./charts/rke2-whereabouts
description: Multus Helm chart for Kubernetes
digest: 1e492c1b4e7156be670ca4899d9de2938fb3743977f188de93db2b36bfd76c30
home: https://github.com/k8snetworkplumbingwg/multus-cni
icon: https://raw.githubusercontent.com/k8snetworkplumbingwg/multus-cni/master/doc/images/Multus.png
maintainers:
- email: charts@rancher.com
name: Rancher Labs
name: rke2-multus
sources:
- https://github.com/intel/multus-cni
type: application
urls:
- assets/rke2-multus/rke2-multus-v4.3.102.tgz
version: v4.3.102- the first item is a chart meant to be used for rke2 1.34-1.36 where both CRD and controller are in the rke2-multus chart (no CRD/controller split)
- the second is meant to be used along with rke2-multus-crd Helm chart (this is what we use today in Sylva for all RKE2 versions)
- the content of
rke2-multus-1.34-1.36is identical to the combination ofrke2-multus+rke2-multus-crd
(credits to @vladonutu for digging on this)
We still need to discuss the long-term solution, but on the short term we would simply need push-helm-artifact to ignore the rke2-multus-1.34-1.36.
Related: we adjusted our CI to not block deployment on failures of push-helm-artifact -> !9946 (merged) and backports