Spin up your own media factory in Kubernetes
These Helm charts are meant to deploy a full-on factory to manage all aspects of your self-hosted media. They utilize the *arr suite of applications for which documentation can be found here.
| App | Description |
|---|---|
| qBittorrent | Handles downloading your non copyrighted media from places like LegitTorrents or the Internet Archive. VPN enabled in case torrents are not allowed on your network. |
| SABnzbd | Newsreader for accessing Usenet resources. VPN enabled as well. |
| Radarr | Movie collection manager |
| Sonarr | Series collection manager |
| Lidarr | Music collection manager |
| Readarr | Book collection manager |
| Prowlarr | Provides indexing service to the other *arr applications |
| Overseerr | Provides a web interface to request media |
| Jellyseerr | Provides a web interface to request media. Integrates with Jellyfin |
| Requestrr | Provides a Discord bot to request media within channels (This project is no longer supported so use at your own risk) |
| Unpackerr | Monitors download directories and unzips any compressed media so the managers can import |
| Flaresolverr | Solves CloudFlare protection for some indexers that need it |
helm repo add genericmediafactory https://mediafactory.charts.bgeneric.net
helm repo update
helm search repo mediafactory
- If you need https access, you have Traefik, Istio, or an external reverse proxy configured.
- You have a Kubernetes cluster deployed (typically a single node k3s or k3d)
- You have Helm installed with access to said cluster
- You have an existing PersistentVolumeClaim set up in the namespace you will deploy to that contains or links to your media library(NFS, etc)
- You are okay with using hostPath for config directories and download directory (you can mount a network share to this hostPath and skip using the PersistentVolumeClaim for the media library)