New Helm Chart Release

[PSanetra]

The latest changes in the master are not yet available via the Helm chart repository. It would be nice to have a new release with the latest changes.

[sdelrio]

Currlently helm fetch downloads vernemq-1.6.7.tgz and the latest is 1.6.8 (https://github.com/vernemq/docker-vernemq/blob/master/helm/vernemq/Chart.yaml)

helm repo add vernemq https://vernemq.github.io/docker-vernemq
helm fetch vernemq/vernemq

[wilfrieddaniels]

I am having the same issue, I was trying to upgrade to 1.6.9 but the helm chart repo only goes up to 1.6.7: https://github.com/vernemq/docker-vernemq/blob/gh-pages/index.yaml

[wilfrieddaniels]

I investigated a bit what should be done, and it seems that simply tagging the appropriate commits with helm-1.6.8 and helm-1.6.9 should trigger a Travis CI task that deploys the new versions to the Helm repo.

Could somebody of the maintainers do this ( @ioolkos ) ? Many thanks!

[onedr0p]

Same here, the helm chart is not being released on updates

[doubliez]

Also trying to use the latest helm chart version, but the latest available in the repo is still 1.6.7

[onedr0p]

We will ever get support from the maintainers, or should we move on? 😔

[ioolkos]

The builds and helm tagging stuff was automated over Travis, and I'm out of Travis build credits. So I need to find a way to duplicate the automation.

---

:point_right: Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq :point_right: Using the binary VerneMQ packages (.deb/.rpm/Docker) requires a subscription.

[onedr0p]

@ioolkos you can use Github workflows instead, with chart-tester and chart-releaser it's pretty simple and best part, it's all free.

See this doc and here are some examples of repositories using these tools:

• https://github.com/toboshii/hajimari
• https://github.com/blakeblackshear/blakeshome-charts

[onedr0p]

@ioolkos Would you accept a PR and champion this to completion? I don't want to contribute if it means waiting months for maintainers to get around to it.

[ioolkos]

@onedr0p thanks for the offer, let me think about that. To be transparent about it, the automation pipeline contributes to the EULA-based Docker images (for which you need a paid subscription when you use them commercially). What's currently missing due to the Travis issue is the tagging of the Helm charts and the automated releases on the github-pages branch.

So even if your code be open source and not directly building anything closed, it'll contribute to the EULA-based packages, in terms of the test and/or build pipeline.

[onedr0p]

Any update @ioolkos ? It's a real bummer this is not getting any attention. It seems like you have 15-30 minutes of work to do to deploy a helm chart release and fix the pipeline.