Open Arceoavs opened 1 year ago
Hello,
To provide another option to deploy on kubernetes, I made an helm chart. All suggestions/bug report are welcome :-)
@Arceoavs It seems relevant here because of k8s, but as I do not intend to hijack your thread, I can move that to another issue if you want.)
Hi,
the helm chart is a good idea as well, @nicolas2bonfils. I think this is relevant in this thread as well, no need to create more issues. One thing about your helm chart: It seems not to create any PersistentVolumeClaim
. That might be a good idea for storing configuration & content.
Totally agree on the PVC
. I made a first version without it because I hesitate between one for all the directory (mounted on a root dir with the subdirectory created inside) or one for each
I ended up creating my own chart because tbh it's really simple and with a common library as basis it's essentially "just" the config i would need to make for my own domains etc anyways https://github.com/maybeanerd/home-cluster/tree/main/charts/audiobookshelf
This could also be easily copied/moved to an official repo because it's extensible, since it supports everything the common lib supports by adding new values
Describe the feature/enhancement
The documentation describes in detail how to deploy audiobookshelf using Docker and docker-compose, with examples given in the repository. However, no such documentation exists for using Kubernetes. Reading through the existing issues, it becomes apparent that some users do deploy the project on Kubernetes clusters, and there are different reasons why this could make sense.
I found that existing community-driven solutions found online, e.g. helm-charts, need to be updated at best and are often even unsafe to use. Thus, I created my own configuration using kustomize. Others might benefit from official documentation about deploying on Kubernetes.
The documentation should look similar to the one using docker-compose and include examples in the repository.