Aleksei SviridkinandClaude d20aac5794 feat(deployment): add envFrom support for ConfigMap/Secret environment variables ...

Add support for loading environment variables from ConfigMap or Secret
resources using envFrom field, following Kubernetes best practices for
configuration management.

Changes:
- Add jellyfin.envFrom parameter in values.yaml
- Add envFrom section in deployment.yaml template (before env)
- Provide comprehensive documentation with examples
- Bump chart version 2.5.0 -> 2.6.0 (minor - new feature)
- Add changelog annotation for Artifact Hub

Use cases:
- Load multiple environment variables from ConfigMap without defining each one
- Load secrets from external secret management systems
- Separate configuration from chart values (12-factor app pattern)
- Simplify configuration for complex deployments

Example usage:
  jellyfin:
    envFrom:
      - configMapRef:
          name: jellyfin-config
      - secretRef:
          name: jellyfin-secrets

Follows standard Kubernetes patterns used by most community Helm charts.

Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>

d20aac5794 · 2025-11-06 13:34:40 +03:00

History

..

_helpers.tpl

chore(jellyfin)!: ♻️ Migrate the helm chart to newer standard level (#40)

2024-11-07 08:15:51 -07:00

deployment.yaml

feat(deployment): add envFrom support for ConfigMap/Secret environment variables

2025-11-06 13:34:40 +03:00

ingress.yaml

chore(jellyfin)!: ♻️ Migrate the helm chart to newer standard level (#40)

2024-11-07 08:15:51 -07:00

persistentVolumeClaim.yaml

Added option for media mount to be a hostpath

2025-04-28 00:09:20 +02:00

service.yaml

fix: 🐛 unify value name and add default (#58)

2025-03-20 07:09:09 -06:00

serviceaccount.yaml

chore(jellyfin)!: ♻️ Migrate the helm chart to newer standard level (#40)

2024-11-07 08:15:51 -07:00

serviceMonitor.yaml

fix: 🐛 unify value name and add default (#58)

2025-03-20 07:09:09 -06:00