search

espocrm / espocrm-docker

Official Docker Image for EspoCRM
https://hub.docker.com/r/espocrm/espocrm
GNU Affero General Public License v3.0
59 stars 36 forks source link

Helm chart for kubernetes deployment #22

Open aschroeder27 opened 1 year ago

aschroeder27 commented 1 year ago

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.

RoSk0 commented 3 months ago

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?

RoSk0 commented 3 months ago

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 .

halvoru commented 2 weeks ago

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.

RoSk0 commented 2 weeks ago

I was wondering how you do updates.

I'm not, updates are handled by the image entrypoint @halvoru .

halvoru commented 2 weeks ago

Yes, I know. I should have been more specific. We run our pods on a network without direct access to the Internet. In general we want a container to be immutable. Running update within the container on our OKD-cluster isn't exactly the way we want to do things. Basically we would like to build a image which we can test in our Dev-project. And after testing we can promote the image to Prod.