Jellyfin on Kubernetes

This project contains the required resources to deploy Jellyfin into Kubernetes. It is adapted from the Jellyfin on Openshift project. The instructions provided here are for microk8s kubernetes running on Ubuntu 22.04 LTS. The jellyfin server will be internet accessible.

Pre-requisites

To deploy this project you will need:

• A working kubernetes cluster. See here for instructions on getting started with microk8s.
• An ingres controller and cert-manager (or something similar) for providing access to the jellyfin service and performing TLS termination. This guide explains how to configure the cert-manager and ingress in microk8s.

Kubernetes resources

The base/ directory contains a PersistentVolumeClaim , a Deployment, Service, and ingress to deploy Jellyfin into Kubernetes.

You will likely need to update the following:

• the ingress controller (see point 1 in the troubleshooting section below).
• the path to the folder on the local machine that contains your media files.

The examples in the project use kustomize to modify configuration parameters. Kustomize is included in recent versions of kubectl and provides a convenient way to adapt a base set of resources to multiple environments. I have included a sample overlay which contains example patches for the above configuration parameters.

Troubleshooting

This project is tested on a microk8s kubernetes cluster running on Ubuntu. It should be mostly portable across different kubernetes implementatoins, however keep in mind:

1. The ingress controller configuration provided in this project ustilises the microk8s ingress and cert-manager addons. If you are using a different kubernets implementation you may need to modify the ingress configuration beyond changing the hostname of your server.
2. You will likely need to set up port forwarding between port 443 on your internet router and the microk8s ingress IP.
3. This example deployment uses the fairly basic 'hostpath' storage for the media library. This will likely be suitable for a home media server running on microk8s or some other lightweight/single node implementation, where the media files are stored in a local directory, but is not suitable for multi-node clusters.
   • An alternative storage option that may be useful if media is on a NAS is to not create a persistent media volume and add media to the library via network shares.
4. Depending on your network configuration, a load balancer service type (instead of ClusterIP) may be necessary to allow media volumes from the local network to be added (I haven't tested this configuration).

TODO List

• For the media persistant volume resource,spec.claimRef.namespace should be set using a kustomize patch.