Aleksei SviridkinandClaude
df3e66c5f9
Add startupProbe to give Jellyfin sufficient time to start, especially with large media libraries or slow storage. This prevents Kubernetes from killing the pod during initial startup phase. Changes: - Add startupProbe configuration in values.yaml with sensible defaults - failureThreshold: 30 (allows up to 5 minutes for startup) - periodSeconds: 10 - Uses tcpSocket check on http port - Update deployment.yaml to include startupProbe from values - Bump chart version 2.5.0 -> 2.5.1 - Add changelog annotation for Artifact Hub Benefits: - Prevents pod restarts during slow initial startup (large media libraries) - Liveness and readiness probes remain responsive after successful startup - Fully configurable and can be disabled by setting startupProbe: null - No breaking changes, backward compatible The startup probe gives Jellyfin up to 5 minutes (30 attempts * 10 seconds) to complete initialization. After the first success, liveness and readiness probes take over with their normal timing. Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Aleksei Sviridkin <f@lex.la>
17 lines
430 B
YAML
17 lines
430 B
YAML
apiVersion: v2
|
|
name: jellyfin
|
|
description: A Helm chart for Jellyfin Media Server
|
|
type: application
|
|
home: https://jellyfin.org/
|
|
icon: https://jellyfin.org/images/logo.svg
|
|
keywords:
|
|
- jellyfin
|
|
- media
|
|
- self-hosted
|
|
version: 2.5.1
|
|
appVersion: 10.11.2
|
|
annotations:
|
|
artifacthub.io/changes: |
|
|
- kind: added
|
|
description: Add startup probe to prevent pod restarts during slow initial startup with large media libraries
|