tag helm releases in the redis-operator repository

[Dariusch]

Is your feature request related to a problem? Please describe.

I am using renovate for dependency updates of my FluxCD HelmReleases, among them the redis-sentinel and redis-replicaiton helm-charts.

My problem is that I cannot properly track or update the HelmRelease with new or even breaking changes because of the current release workflow.

As far as I understand, you moved the charts into this repo and create the git tag in the helm-charts repository to upload the chart release into the existing chart index.

The source link, links to the deprecated helm-charts repository. The version tag and the compare link point to the git tag in the helm-chart repository. The diff between the versions is meaningless as the source files are in a different (this) repository.

Describe the solution you'd like

e.g. git tags for every chart version bump in this repository, e.g. helm-redis-sentinel-v0.16.6 to compare the tags to an older release.

Describe alternatives you've considered

One alternative is to get into a deep search of the old commit hash of the Chart.yaml of the previous version and make a diff to the recently released one, which is tedious.

The other one is diffing it locally, e.g.:

helm repo add ot-helm https://ot-container-kit.github.io/helm-charts/

helm pull ot-helm/redis-sentinel --version '0.16.5'  --untar --destination rs165
helm pull ot-helm/redis-sentinel --version '0.16.6'  --untar --destination rs166
diff rs165 rs166

What version of redis-operator are you using?

redis-operator version: latest

Additional context

Is there any chance we can enhance the current workflow to make the helm-charts and the process more maintainable?

[drivebyer]

I'm not sure I understand your meaning. Did you mean that we need an additional GitHub Action to handle the chart release process?

[Dariusch]

The question is simple:

How can I easily see the diff between 2 chart versions in this repository?

Currently, it is only possible to diff it locally or via a git compare of the commit hashes. There are no tags for helm releases

[drivebyer]

I understand. We can use the diff tool as you suggested. However, in my opinion, it's not the responsibility of this repository to handle the diff check. Could you please provide more guidance or suggestions?

[Dariusch]

I'd be completely fine if there were just git tags associated with a new helm release.