jellyfin: replace redis Deployment with valkey-operator instance #367

Merged
benvin merged 1 commits from benvin/jellyfin-valkey into main 2026-08-15 14:54:06 +10:00

1 Commits

Author SHA1 Message Date
unkin-agent da91f46e07 jellyfin: replace redis Deployment with valkey-operator instance
ci/woodpecker/pr/vector-test Pipeline was successful
ci/woodpecker/pr/pre-commit Pipeline was successful
ci/woodpecker/pr/kubeconform Pipeline was successful
Swap Jellyfin's self-managed redis Deployment for a valkey-operator-managed
single-instance ValkeyCluster (shards:1, replicas:0) as the distributed
transcode-session store, and point Jellyfin at the operator's client Service.

- Add apps/base/jellyfin/valkey.yaml: ValkeyCluster jellyfin-valkey, image via
  artifactapi dockerhub mirror, exporter disabled, redis-parity resources, no
  persistence (emptyDir) since the lease state is ephemeral and the managed PVC
  cannot carry the k8up.io/backup annotation the namespace Schedule needs.
- Remove redis-deployment.yaml, redis-service.yaml, redis-pvc.yaml and drop them
  from kustomization.yaml; add valkey.yaml.
- Repoint Jellyfin__TranscodeStore__RedisConnectionString at the operator client
  Service (valkey-jellyfin-valkey:6379), preserving abortConnect=false and the
  LeaseDurationSeconds. No auth/TLS: the operator leaves the default user
  passwordless with protected-mode off (parity with the old open redis).

HA (more shards/replicas) is a follow-up.
2026-08-15 13:50:11 +10:00