Files
k3s-cluster/jellyfin/ingress.yaml
Roger Oriol 66433ff0b1 fix tls: use letsencrypt-prod cluster-issuer for jellyfin/n8n/qbittorrent/myorg/phoenix/fava
The ingresses referenced a Cloudflare OriginIssuer 'prod-issuer' whose CRD
and controller are not installed in the cluster, so cert-manager could not
issue certs and Traefik served a default cert (invalid SSL). Switch to the
existing letsencrypt-prod ClusterIssuer with specific hostnames + per-app
secrets, matching the working ingresses (http-01 cannot issue wildcards).
2026-06-23 11:46:38 +02:00

27 lines
634 B
YAML

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: jellyfin-ingress
namespace: jellyfin
annotations:
kubernetes.io/ingress.class: "traefik"
traefik.ingress.kubernetes.io/redirect-entry-point: https
traefik.ingress.kubernetes.io/compress: "true"
cert-manager.io/cluster-issuer: letsencrypt-prod
spec:
tls:
- hosts:
- jellyfin.rogi.casa
secretName: jellyfin-tls
rules:
- host: jellyfin.rogi.casa
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: jellyfin
port:
number: 80