Skip to content

Helm oci image version and versions in helm-release mismatch for release v0.5.0 #742

@tjololo

Description

@tjololo

Description

Observed Behavior: When trying to deploy version v0.5.0 with flux the reconciliation failed due to the oci image and the version specified in the Chart.yaml file didn't match. And flux helm controller reports the error: artifact revision 0.5.0 does not match chart version v0.5.0-rc.1
Further investigations also reveals that the appVersion and image.tag values seems to be wrong (also v0.5.0-rc.1) this I think should also be v0.5.0

Expected Behavior: OCI image tag and Chart.yaml version, appVersion and values.yaml image.tag matches

Reproduction Steps (Please include ResourceGraphDefinition and Instances files):
To verify this is used the fluxcli to download and view the file inside the OCI image:

mkdir /tmp/kro-v0.5.0
flux pull artifact oci://registry.k8s.io/kro/charts/kro:v0.5.0 --output /tmp/kro-v0.5.0
cat /tmp/kro-v0.5.0/kro/Chart.yaml

This will output the following:

apiVersion: v2
appVersion: v0.5.0-rc.1
description: A Helm chart for kro
home: https://kro.run/
name: kro
type: application
version: v0.5.0-rc.1

Checking the values.yaml reveals that the image.tag also is v0.5.0-rc.1:

$ cat /tmp/kro-v0.5.0/kro/values.yaml | yq '.image.tag'
v0.5.0-rc.1

Versions:

  • kro version: 0.5.0
  • Kubernetes Version (kubectl version): 1.34.1

Involved Controllers: N/A

  • Controller URLs and Versions (if applicable): N/A

Error Logs (if applicable)**:
Flux helmrelease status:

$ kubectl get helmreleases.helm.toolkit.fluxcd.io -n kro kro             
NAME   AGE     READY   STATUS
kro    6m43s   False   artifact revision 0.5.0 does not match chart version v0.5.0-rc.1

Seems to me that the build logs output values that would suggest that the build is correct.

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Which option describes the most your issue?

Others (please specify)

Released helm artifact and helm install

Metadata

Metadata

Assignees

Labels

kind/bugCategorizes issue or PR as related to a bug.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions