-
Notifications
You must be signed in to change notification settings - Fork 132
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
[Kubernetes] Add Kubernetes Helm Chart for Docspell #2502
Comments
… templates into the correct directories.
…cret values for the restserver.
…cret values for the restserver.
…d secret values.
…d secret values.
…d secret values.
…d secret values.
…d secret values.
I've published a first version of the helm chart here: Anyone's free to test around with this and suggest any improvements ^^ |
Thanks so much for submitting this. |
AFAIK, GitHub has a package registry for public repos, right? I thought Helm was included there. I hosted it on my own git instance, for testing purposes. When I started this, I wasn't really concerned about what registry it would end up on, I just wanted to start the discussion and development of one. |
Let me know if I can help with anything hosting related. There should be (i hope) some options. |
Mhh I think it would be worth looking into artifact hub. If we want to make a helm chart available @eikek, we'll need some registry to host it. |
btw I've been using my own chart for a couple of months now: https://github.com/pschichtel/helm-charts/tree/main/charts/docspell |
Nice work! I see you went the route of just supplying the entire config as the docspell.conf file. |
Hi there, I had some thought about the k8s setup: I will sooner or later move the docker setup into a separate repo, because it becomes too tedious to maintain for me. I was thinking to also create a separate repo in the docspell org for the helm setup. Both of you could be committers there and do whatever, whenever you like. (it could also build the docker images) WDYT? For me, the repo becomes a bit too heavy. @waldher @TheAnachronism (and whoever else likes) |
Mhhh, yeah why not. |
I don't care how to organize, tbh. Would leave that all to you 😄 We can as well have docker + kubernetes in one repo, perhaps not so bad an idea? I had the idea with the separate repo for the docker images for a while now. Now with the kubernetes setup, I thought that it could live next to each other, or be a separate repo as well. |
For starters, I think it would be OK if we have one repo for all the containerization stuff. So docker and different Kubernetes deployment options (Helm and Kustomize, I'd say) If we later need to pull out the helm chart, that shouldn't be much of a problem, I think. |
I'm finally able to pick this topic up again. |
Thanh you @TheAnachronism ! Yes, I think a separate repo would be great. I can create one in the docspell org and assign you to it. Or you can also do it under your account name? What do you prefer? Also, the hard part, what name to choose :-)? |
Lets just call it docker and have it under the Docspell org. I'll look into how the helm chart can be properly hosted ^^ |
It looks like with a GitHub pages set up, the helm chart can be hosted on there. Maybe this page can then be published under helm.docspell.org or whatever. |
I have a working setup with chart-releaser that I can contribute. |
Also, @eikek, do you have an email I could reach you on? Had a look at your profile and wanted to ask you something directly ^^ |
Sorry for the delay, I'm currently away. I created the repo at docspell/docker and added both of you (@pschichtel + @TheAnachronism) as maintainers. You can reach me at info [at] docspell.org via E-Mail. |
An often used strategy to deploy something to Kubernetes is per Helm chart. This way, people only have to specify their settings inside a
values.yaml
file and the chart will take care of generating the correct Kubernetes manifests and configs for the entire application and its dependencies.Docspell already has somewhat of a Kubernetes deployment with Kustomize, where I've tried to fix some issues in #2498.
The text was updated successfully, but these errors were encountered: