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

Package Manager for HiveMQ CE #67

Open
dobermai opened this issue Jul 30, 2019 · 3 comments
Open

Package Manager for HiveMQ CE #67

dobermai opened this issue Jul 30, 2019 · 3 comments
Labels
feature Contributions welcome!

Comments

@dobermai
Copy link
Member

HiveMQ CE should be available via Package Manager like Homebrew, deb, RPM, ... to ease the installation process. This should be part of every community release to trigger a job that releases the new HiveMQ Version for all Package Manager.

@dobermai dobermai added the feature Contributions welcome! label Jul 30, 2019
@sbaier1 sbaier1 changed the title Package Manager für HiveMQ CE Package Manager for HiveMQ CE Jul 30, 2019
@frittentheke
Copy link

frittentheke commented Jan 27, 2020

@dobermai @sbaier1 while you are "at it" ... please consider providing a Helm3 chart for deployments on Kubernetes. With your nice discovery extension (https://github.com/hivemq/hivemq-dns-cluster-discovery-extension) and the Docker images ready for Kubernetes, this would be an awesome addition to get HiveMQ up an running in such environments as well.

@fraschbi
Copy link
Contributor

fraschbi commented Feb 3, 2020

HI @frittentheke,

Thank you for the input.
This is the HiveMQ Community Edition Repository. Clustering is not included in that version.

Regards,
Florian

@frittentheke
Copy link

@fraschbi fair point about the clustering being available in the commercial editions only.

Still a Helm chart is what the cool cloud kids require to deploy onto Kubernetes nowadays - Single node or clustered.
And apart from this general point about proving Helm chart, what keeps you from providing mostly the same Helm chart for CE as well as for the other editions? Just add a variable to chose the edition which then switches the container image as well.

To help with "marketing" the potential feature upsell, there could be a comment line in the values.yaml just above the "clustering:" section stating that this requires a license which you could prepare a Secret/ConfigMap template (https://helm.sh/docs/chart_template_guide/accessing_files/#configmap-and-secrets-utility-functions) for.

A common and well maintained Helm Chart would just be a great addition.

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

No branches or pull requests

3 participants