You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Chart repository doesn't facilitate easy navigation to chart releases for comparisons from release to release.
Describe the solution you'd like
At the time that a particular chart is released, a GitHub release and/or tag should be created. This would be used for comparing releases for audit and changelog purposes.
Describe alternatives you've considered
Unfortunately, this is a problem propagated by helm/charts with managing multiple charts within a single repository. I don't know of any good examples of other monolithic repos of various components successfully creating tags/releases off subsections, which is why I'm somewhat against this pattern to begin with. I took a long shot looking at alpinelinux/aports releases, which builds alpine packages for alpine linux distribution; they release / tag as this forms the version being released whereas helm chart monolithic repos don't work the same.
Thanks for taking a moment to consider as I haven’t seen anyone demonstrate a solution around this. Even if it ultimately proves infeasible, I’m grateful for the dialogue
Is your feature request related to a problem? Please describe.
Chart repository doesn't facilitate easy navigation to chart releases for comparisons from release to release.
Describe the solution you'd like
At the time that a particular chart is released, a GitHub release and/or tag should be created. This would be used for comparing releases for audit and changelog purposes.
Describe alternatives you've considered
Unfortunately, this is a problem propagated by helm/charts with managing multiple charts within a single repository. I don't know of any good examples of other monolithic repos of various components successfully creating tags/releases off subsections, which is why I'm somewhat against this pattern to begin with. I took a long shot looking at alpinelinux/aports releases, which builds alpine packages for alpine linux distribution; they release / tag as this forms the version being released whereas helm chart monolithic repos don't work the same.
Additional context
The text was updated successfully, but these errors were encountered: