Official helm chart

[M0NsTeRRR]

Description

Some users, like myself, run Jellyseerr in a Kubernetes environment, so it would be beneficial to have a community-driven Helm chart. I’m creating this issue to track progress, as I’ll be handling the task.

Desired Behavior

.

Additional Context

No response

Code of Conduct

• I agree to follow Jellyseerr's Code of Conduct

[djjudas21]

I'm interested in this feature and happy to help if needed 🙂 I already maintain several Helm charts.

[M0NsTeRRR]

Hey, thanks! I’ll have time this weekend to finish it.
The Helm chart is already prepared, as I’ll be moving mine to the Jellyseerr repository, and we can start from there. 🙂
https://github.com/M0NsTeRRR/helm-charts/tree/main/charts/jellyseerr

[djjudas21]

Ah cool, I thought I recognised your username fron somewhere 😁

[M0NsTeRRR]

From k8s discord or from some FOSS contribution could be ahah :)

[M0NsTeRRR]

This is the first pull request to add the base Helm chart along with the lint workflow. The release workflow requires further discussion to determine how it can be implemented with minimal impact on the Jellyseerr maintainers' workload.

[M0NsTeRRR]

As discussed on Discord, we want to avoid creating a new release for each Helm chart change.
Since GitHub Pages is already used for Jellyseerr documentation (if we can avoid conflict between usage), moving forward, we could utilize the "new" (released in 2022) Helm repository setup (OCI instead of plain tar.gz).

https://helm.sh/docs/topics/registries/

I experimented with the OCI registry last weekend, and I plan to create a PR this weekend with the associated documentation.
In the meantime, @djjudas21, have you looked at the current Helm chart implementation? If so, you could add anything you think would be useful or could be better handled to avoid breaking changes after the first release. 😊