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

bug: Inconsistent image tagging in Helm chart appVersion #125

Open
3 tasks done
mihaigalos opened this issue Feb 27, 2024 · 10 comments · May be fixed by #129
Open
3 tasks done

bug: Inconsistent image tagging in Helm chart appVersion #125

mihaigalos opened this issue Feb 27, 2024 · 10 comments · May be fixed by #129

Comments

@mihaigalos
Copy link

Preflight Checklist

  • I agree to follow the Code of Conduct that this project adheres to.
  • I have searched the issue tracker for an issue that matches the one I want to file, without success.
  • I am not looking for support or already pursued the available support channels without success.

Chart

dex

Version

v2.37.0

Expected Behavior

Consistent tagging between appVersion and image tag between Chart.yaml and values.yaml.

Actual Behavior

Currently, releases contain Helm charts which have Chart.yaml appVersion: "X.YY.Z". But the values.yaml tag references a different format (vX.YY.Z), also instructing users that if you don't specify anything, the appVersion is used.

We are automatically updating upstream charts with PRs which are automatically opened in our internal repos, this behavior impedes us.

Please help. Thank you.

Steps To Reproduce

No response

Additional Information

No response

Values

No response

@sagikazarmark
Copy link
Member

Although this is taken care of in the deployment template here, I agree it would be easier to use the same tag as version.

I'm not entirely sure I understand how it impedes you, though.

@mihaigalos
Copy link
Author

We have an automatic update mechanism that looks at this repo's releases, matches the release with gh-pages branch :: index.yaml :: appVersion.
It then takes that appVersion and considers it as a tag (same way it's described) and that is then used as the image to be used with the release.

Other projects to it the same way - examples:

Don't get me wrong, it ca be vX.Y.Z or X.Y.Z, but at least consistent between the Chart.yaml and index.yaml

@sagikazarmark
Copy link
Member

Don't get me wrong, it ca be vX.Y.Z or X.Y.Z, but at least consistent between the Chart.yaml and index.yaml

You mean git tag and appVersion, don't you?

@mihaigalos
Copy link
Author

So probably also that would have to be unified as well.. 😅

But we are not consuming that, attribute. I'm refering to Chart.yaml and index.yaml.

@sagikazarmark
Copy link
Member

I don't see how Chart.yaml and index.yaml can differ. index.yaml is created based on Chart.yaml.

When no tag is specified in values, the prefix is automatically prepended to the value of appVersion.

What we can do, is remove that automatic prefixing and use the full tag in appVersion instead.

Can't really change anything else. Not sure if this would solve your problem though.

@mihaigalos
Copy link
Author

What we can do, is remove that automatic prefixing and use the full tag in appVersion instead.

That would definitely help! 😄

@mihaigalos
Copy link
Author

Hi @sagikazarmark, do you need any help with this? I can provide a PR if you think it's worthwhile.

@sagikazarmark
Copy link
Member

@nabokihms what do you think?

I'm not against the above outlined solution.

@nabokihms
Copy link
Member

I'm ok with this change if we speak about removing the automatic v prefix.

@mihaigalos mihaigalos linked a pull request Apr 17, 2024 that will close this issue
3 tasks
@mihaigalos
Copy link
Author

Hi. Any news here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants