FIWARE / helm-charts

:globe_with_meridians: Kubernetes HELM Charts for FIWARE Generic Enablers for provisioning scalable, production-ready powered-by-FIWARE installations based around NGSI Context Brokers and other components

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Domibus

bhack opened this issue · comments

commented

As Domibus was added again as third party in the Fiware catalog do you plan to add a Domibus chart?

I found an helm chart example in:
https://github.com/dladlk/delis/tree/dev/delis-test-server/helm

Hi @bhack ,
we don't have such plans, yet. But we are open for contributions, so a PR would be welcome:)

commented

As @dladlk has done the majority of the work there it could be interesting to se if they want to "upstream" it here and on https://artifacthub.io/

These helm charts are mostly for test purposes on our DEV server to simplify upgrades of Domibus.
The main challenge with Helm was to have some convenient way to customize domibus.properties - so the base file is used from default deliveries (as more and more new configs are added), and we wanted to be able to overwrite, comment out or add there new configs via env properties - so added a small java program which reads env variables and modifies given *.properties file (not ideal).
The result helm chart is very specific, so on PROD we always use domibus.properties via mounts or secrets and actually use pure *.yaml files without Helm (especially, when Kubernetes migrated to Deployment apps/v1 and Helm just stopped working without manual history modification)...

Conclusion - you can look there for inspiration, but it is far away from being enough reusable and flexible :)

commented

The main challenge with Helm was to have some convenient way to customize domibus.properties

Yes It is not only a challenge for HELM but also for a more traditional deployment as you need to maintain patching scripts over the default conf.