-
Notifications
You must be signed in to change notification settings - Fork 35
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
Helm chart for kubernetes deployment #22
Comments
Hi, we, Catalyst, are using EspoCRM internally for number of years now and for our own and the community benefit decided to create a Helm chart and open source it. I am working on it and already have a proof of concept running. Expecting to have MVP version in the next couple of weeks. From our point of view, this Helm chart repository should be part of the EspoCRM group/organization. @yurikuzn @tmachyshyn would you be willing accept that? If so, what do you see as the next steps? |
A bit upsetting to have no feedback from maintainers in almost two weeks... I believe MVP version is ready and functional. It was tested on production cluster and all the main function like, update from version to version, jobs daemon, WebSocket are all functional. Surely it has bug and things could be improved, but that will come later with the feedback from the real users. Meanwhile, we are eager start using it in production set up, so until we have a permanent residency for it, it is published here https://gitlab.com/kroskolii/espocrm-chart . |
Hi, I had a look at your helm chart, and we something similar. However, I was wondering how you do updates. We also mount "/var/www/html" as a PV. |
I'm not, updates are handled by the image entrypoint @halvoru . |
Yes, I know. I should have been more specific. |
Is your feature request related to a problem? Please describe.
I want to deploy EspoCRM in a local kubernetes cluster, but there is no official helm chart.
Describe the solution you'd like
This would be solved by providing an official helm chart.
The text was updated successfully, but these errors were encountered: