Release Process of the helm-chart(s)

[moreinhardt]

I'm not sure I understand how this tool is being published.

• There is a chart in this repo that's at version 1.2.2. and appVersion 2.3 according to its Chart.yaml which was last changed 1 year ago.

• There is the chart in the delivery-hero repo which is also published to the OCI registry which is currently at version 1.1.9 and appVersion 2.1 according to its Chart.yaml which was last changed 8 months ago.

• There is a very recent release of version 2.4 in this repo but it's not in any helm-chart yet.

Besides the version skew between the two charts there seems to be a diff too when I look at the values.yaml and Chart.yaml, but I may be wrong.

---

Is it intended, that these two charts evolve independently?

If yes, will the OCI-published chart get an update to the latest version?

If no, any chance that the chart from this repo gets published to an OCI registry?

Is it intended, that the latest app release does not also have a related helm-chart release that makes use of it?

---

Thank you very much for creating and maintaining this neat tool!

[max-rocket-internet]

Hey @moreinhardt 👋

You're right in all those observations. The reason is that I just accept pull requests now, I'm not really making an effort to update all the charts.

Is it intended, that these two charts evolve independently?

Not intentional but the one deliveryhero/helm-charts/stable/k8s-event-logger is better I think.

Is it intended, that the latest app release does not also have a related helm-chart release that makes use of it?

Not intended, no.

I would suggest we:

1. Delete the chart in this repo
2. Update the chart in deliveryhero/helm-charts/stable/k8s-event-logger

[max-rocket-internet]

FYI I've updated the helm chart in this PR: https://github.com/deliveryhero/helm-charts/pull/740