Skip to content

Jellyfin does not work with tailscale disabled #67

Description

@thiagocrepaldi

By creating a jellyfin values.yaml with

  tailscale:
    enabled: false
    sidecar:
      enabled: false
      existingAuthSecret: "tailscale-auth"

and running kubectl get pods -n media, servarr-jellyfin-* will not be listed

By executing kubectl get events -n media --sort-by='.lastTimestamp' we get something like

LAST SEEN   TYPE      REASON             OBJECT                                      MESSAGE
39m         Normal    Scheduled          pod/servarr-qbittorrent-7f45b8956b-cc5js    Successfully assigned media/servarr-qbittorrent-7f45b8956b-cc5js to k3s-node-01
39m         Normal    Killing            pod/servarr-qbittorrent-7f45b8956b-ndxgm    Stopping container servarr
39m         Normal    SuccessfulCreate   replicaset/servarr-qbittorrent-7f45b8956b   Created pod: servarr-qbittorrent-7f45b8956b-cc5js
39m         Normal    Pulled             pod/servarr-qbittorrent-7f45b8956b-cc5js    Container image "lscr.io/linuxserver/qbittorrent:latest" already present on machine and can be accessed by the pod
39m         Normal    Created            pod/servarr-qbittorrent-7f45b8956b-cc5js    Container created
39m         Normal    Started            pod/servarr-qbittorrent-7f45b8956b-cc5js    Container started
2m55s       Warning   FailedCreate       replicaset/servarr-jellyfin-859fdfff5d      Error creating: pods "servarr-jellyfin-859fdfff5d-" is forbidden: error looking up service account media/jellyfin-tailscale: serviceaccount "jellyfin-tailscale" not found

Even though I am not trying to use Tailscale (I am using tailscale operator separate from this values.yaml), the Helm chart template is hard-coded to look for a ServiceAccount named jellyfin-tailscale to associate with the Jellyfin Pod. Because that ServiceAccount doesn't exist in my media namespace, the Kubernetes Admission Controller is rejecting the creation of the Pod entirely.

I noticed that jellyfin: doesnt have a serviceAccount section like sonarr and the others. was that intended?

To workaround the problem and verify my theory, i created a dummy serviceAccount jellyfin-tailscale and reappliedservarr-values.yaml. Worked like a charm

 kubectl create serviceaccount jellyfin-tailscale -n media
thiago@k3s-node-01:~/dev/gh/k8s-zoo/apps/plex$ kubectl get pods -n media
NAME                                    READY   STATUS    RESTARTS   AGE
plex-plex-media-server-0                2/2     Running   0          20h
servarr-bazarr-5bcfbc7bb5-k9496         1/1     Running   0          46h
servarr-cleanuparr-ccc7999cd-vnt76      1/1     Running   0          46h
servarr-flaresolverr-79cd7f6676-q2n87   1/1     Running   0          46h
servarr-jellyfin-bd8bd9cdf-s9tl9        1/1     Running   0          21s
servarr-lidarr-7b6776b59c-4qc4n         1/1     Running   0          46h
servarr-prowlarr-6fc9498d5d-2cdnw       1/1     Running   0          46h
servarr-qbittorrent-7f45b8956b-cc5js    1/1     Running   0          52m
servarr-radarr-58f5976d79-qtkk9         1/1     Running   0          46h
servarr-seerr-7b9c7b7db8-rmv2d          1/1     Running   0          46h
servarr-sonarr-9db79f4fd-fttpv          1/1     Running   0          46h

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions