88 Commits

Include renames

• Merge branch 'master-vnext' into feature/add-network-policy
  Aleksei Sviridkin 2025-11-08 04:15:48 +03:00
  1cf3d1130c
• test(deployment): add revisionHistoryLimit tests and deployment notes

  Add helm-unittest tests for revisionHistoryLimit:
  - Default value (3) verification
  - Custom values support (0, 1, 5, 100)
  - Ability to disable revision history
  
  Add NOTES.txt with revisionHistoryLimit information:
  - Show configured revision history limit
  - Warning when disabled (0)
  - Note for minimal history (1)
  - Rollback command example for normal values
  
  This parameter controls how many old ReplicaSets are retained
  for rollback purposes, reducing etcd storage usage.
  
  Co-Authored-By: Claude <noreply@anthropic.com>
  Signed-off-by: Aleksei Sviridkin <f@lex.la>

  Aleksei SviridkinandClaude 2025-11-07 17:43:20 -07:00
  e1bcdc003b
• feat(deployment): add revisionHistoryLimit parameter for rollback history control

  Add revisionHistoryLimit parameter to control how many old ReplicaSets are
  retained for rollback purposes, reducing etcd storage usage compared to
  Kubernetes default of 10.
  
  Changes:
  - Add revisionHistoryLimit parameter in values.yaml (default: 3)
  - Add revisionHistoryLimit to deployment.yaml spec
  - Provide comprehensive documentation with recommendations
  - Bump chart version 2.5.0 -> 2.5.1 (patch - minor enhancement)
  - Add changelog annotation for Artifact Hub
  
  Benefits:
  - Reduce etcd storage usage (especially important in large clusters)
  - Maintain reasonable rollback capability (3 previous versions)
  - Allow customization based on deployment needs
  - Can be set to null to use Kubernetes default (10)
  
  Default rationale:
  - 3 revisions provides sufficient rollback capability for most use cases
  - Reduces cluster resource usage (etcd storage, API server load)
  - Follows best practices from production Kubernetes deployments
  - Users can override if they need more history
  
  Example usage:
    # Use default (3 revisions)
    revisionHistoryLimit: 3
  
    # Increase for critical deployments
    revisionHistoryLimit: 10
  
    # Use Kubernetes default (10)
    revisionHistoryLimit: null
  
    # Disable history (not recommended)
    revisionHistoryLimit: 0
  
  See: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#revision-history-limit
  
  Co-Authored-By: Claude <noreply@anthropic.com>
  Signed-off-by: Aleksei Sviridkin <f@lex.la>

  Aleksei SviridkinandClaude 2025-11-07 17:43:20 -07:00
  68ebc46dbd
• docs(readme): regenerate README.md from template with helm-docs

  Regenerate README.md from README.md.gotmpl template using helm-docs.
  
  This adds the complete NetworkPolicy documentation section and updates
  the values table with all networkPolicy configuration parameters.
  
  The generated documentation includes:
  - Updated version badge (2.6.0)
  - Complete networkPolicy values table with descriptions
  - Network Security section with examples and troubleshooting
  - All parameters from values.yaml with auto-generated descriptions
  
  Co-Authored-By: Claude <noreply@anthropic.com>
  Signed-off-by: Aleksei Sviridkin <f@lex.la>

  Aleksei SviridkinandClaude 2025-11-07 19:30:56 +03:00
  5be9dae420
• chore(chart): bump version to 2.6.0 with NetworkPolicy support

  Bump chart version from 2.5.0 to 2.6.0 (minor version) for new feature.
  
  Added artifacthub.io/changes annotations:
  - NetworkPolicy support for network isolation and security hardening
  - NOTES.txt with deployment status and configuration summary
  
  This is a backward-compatible change:
  - NetworkPolicy is disabled by default
  - Existing installations will not be affected
  - Users can opt-in to NetworkPolicy by setting networkPolicy.enabled=true
  
  The NetworkPolicy feature provides enterprise-grade network security
  controls for Jellyfin deployments in Kubernetes environments with
  CNI plugin support.
  
  Co-Authored-By: Claude <noreply@anthropic.com>
  Signed-off-by: Aleksei Sviridkin <f@lex.la>

  Aleksei SviridkinandClaude 2025-11-07 19:29:18 +03:00
  a7cfada436
• docs(readme): add comprehensive NetworkPolicy documentation

  Add "Network Security" section to README.md.gotmpl with:
  
  Requirements:
  - CNI plugin support (Calico, Cilium, Weave, Canal)
  - DLNA incompatibility explanation
  
  Configuration examples:
  - Basic usage (default settings)
  - Production configuration (Ingress controller only)
  - High security (restricted egress)
  - Monitoring integration (Prometheus)
  - Advanced scenarios (multiple namespaces, custom rules)
  
  Security considerations:
  - Metadata provider requirements (TMDB, TheTVDB, OpenSubtitles)
  - DNS access importance
  - Local metadata alternative
  - Testing recommendations
  
  Troubleshooting guide:
  - Metadata download issues
  - Web interface access problems
  - Prometheus scraping failures
  - Deployment validation errors
  
  The documentation provides complete guidance for users to implement
  NetworkPolicy according to their security requirements, from basic
  isolation to zero-trust configurations.
  
  Co-Authored-By: Claude <noreply@anthropic.com>
  Signed-off-by: Aleksei Sviridkin <f@lex.la>

  Aleksei SviridkinandClaude 2025-11-07 19:28:57 +03:00
  5bfd629848
• test(networkpolicy): add comprehensive helm-unittest test suite

  Add 20+ unit tests for NetworkPolicy template covering:
  
  Creation conditions:
  - Not created by default (enabled: false)
  - Created when enabled: true
  - Fails with clear error when hostNetwork + NetworkPolicy enabled
  - Fails when DLNA + NetworkPolicy enabled
  
  Ingress rules:
  - Default allowExternal behavior (no 'from' restriction)
  - Restricted access with podSelector/namespaceSelector
  - Custom ingress rules application
  - Automatic Prometheus ingress when metrics enabled
  - Prometheus namespace selector when specified
  
  Egress rules:
  - DNS egress with default kube-system/kube-dns
  - Custom DNS namespace and pod selector
  - AllowAllEgress default behavior
  - Restricted egress modes (metadata, in-cluster)
  - Custom CIDR blocks
  - Custom egress rules application
  - DNS disabled scenario
  
  Policy configuration:
  - Correct policyTypes (Ingress, Egress)
  - Pod selector labels matching chart labels
  
  Tests ensure NetworkPolicy works correctly across all supported
  configurations and fails safely when misconfigured.
  
  Co-Authored-By: Claude <noreply@anthropic.com>
  Signed-off-by: Aleksei Sviridkin <f@lex.la>

  Aleksei SviridkinandClaude 2025-11-07 19:28:38 +03:00
  aaa9c91a8e
• feat(templates): add NOTES.txt with deployment status information

  Add NOTES.txt template that displays helpful information after deployment:
  - How to access Jellyfin (via Ingress or port-forward)
  - NetworkPolicy status and configuration summary when enabled
    - Ingress policy details (allowExternal, selectors, Prometheus)
    - Egress policy details (DNS, internet access, restrictions)
    - Warnings for misconfigurations (no selectors, DNS disabled)
    - Compatibility note about CNI requirements
  - Warning if NetworkPolicy + hostNetwork are both enabled
  
  The NOTES provide immediate visibility into the deployment configuration
  and help users quickly identify and troubleshoot network access issues.
  
  Co-Authored-By: Claude <noreply@anthropic.com>
  Signed-off-by: Aleksei Sviridkin <f@lex.la>

  Aleksei SviridkinandClaude 2025-11-07 19:28:13 +03:00
  32494dd1fd
• feat(values): add networkPolicy configuration section

  Add networkPolicy section to values.yaml with comprehensive configuration options:
  - enabled: boolean flag to enable/disable NetworkPolicy (default: false)
  - policyTypes: configure Ingress and/or Egress policies
  - ingress: control which pods/namespaces can access Jellyfin
    - allowExternal: permit access from any namespace (default: true)
    - podSelector/namespaceSelector: restrict access to specific pods/namespaces
    - customRules: advanced ingress rules for complex scenarios
  - egress: control outbound connections from Jellyfin
    - allowDNS: permit DNS resolution (default: true, required)
    - allowAllEgress: permit all internet access (default: true)
    - restrictedEgress: high-security mode with HTTPS-only metadata access
    - customRules: advanced egress rules
  - metrics: automatic Prometheus integration configuration
  
  All parameters include detailed documentation explaining:
  - Purpose and usage
  - Default values and recommended settings
  - Examples for common scenarios
  - Security implications
  
  The configuration supports use cases from simple deployments to
  zero-trust environments while maintaining sensible defaults.
  
  Co-Authored-By: Claude <noreply@anthropic.com>
  Signed-off-by: Aleksei Sviridkin <f@lex.la>

  Aleksei SviridkinandClaude 2025-11-07 19:27:55 +03:00
  d2051f1dfe
• feat(templates): add NetworkPolicy template with ingress/egress rules

  Add comprehensive NetworkPolicy support for Jellyfin pod with:
  - Ingress rules: configurable external access or namespace/pod selectors
  - Egress rules: DNS resolution, metadata providers, custom rules
  - Automatic Prometheus integration when metrics are enabled
  - DLNA/hostNetwork detection with fail-safe error message
  - Support for restrictedEgress mode for high-security environments
  
  The NetworkPolicy is disabled by default to maintain backward compatibility.
  When enabled, it provides fine-grained control over network traffic:
  - Who can access Jellyfin (ingress)
  - What external connections Jellyfin can make (egress)
  
  NetworkPolicy requires CNI plugin support (Calico, Cilium, etc.) and
  cannot be used with hostNetwork mode (DLNA). The template includes
  validation to prevent misconfiguration.
  
  Co-Authored-By: Claude <noreply@anthropic.com>
  Signed-off-by: Aleksei Sviridkin <f@lex.la>

  Aleksei SviridkinandClaude 2025-11-07 19:27:38 +03:00
  24fa95525a
• docs(charts): 📝 write updated reademe
  github-actions[bot] 2025-11-03 03:47:15 +00:00
  2401a45bb1
• chore(jellyfin): Bump chart version to 2.5.0 and set appVersion to 10.11.2
  github-actions[bot] 2025-11-03 03:47:07 +00:00
  2c1f2a526c
• docs(charts): 📝 write updated reademe
  github-actions[bot] 2025-11-03 03:46:43 +00:00
  464c663c92
• feat: allow to enable or disable some pod privileges (#82)
  Benoît Sauvère 2025-11-02 20:46:36 -07:00
  39cb96db5d
• docs(charts): 📝 write updated reademe
  github-actions[bot] 2025-11-03 03:46:27 +00:00
  969f7b8885
• Update jellyfin/jellyfin Docker tag to v10.11.2 (#85)
  renovate[bot] 2025-11-02 20:46:19 -07:00
  8a0fcbda21
• docs(charts): 📝 write updated reademe
  github-actions[bot] 2025-10-27 07:04:09 +00:00
  9fbd74d9b7
• Update jellyfin/jellyfin Docker tag to v10.11.1
  renovate[bot] 2025-10-27 03:30:07 +00:00
  2e5386532e
• docs(charts): 📝 write updated reademe
  github-actions[bot] 2025-10-20 03:31:47 +00:00
  5464aa942e
• chore(jellyfin): Bump chart version to 2.4.0 and set appVersion to 10.11.0
  github-actions[bot] 2025-10-20 03:31:37 +00:00
  aff38deb68
• docs(charts): 📝 write updated reademe
  github-actions[bot] 2025-10-20 03:29:56 +00:00
  03f319d762
• Update jellyfin/jellyfin Docker tag to v10.11.0 (#80)

  Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

  renovate[bot] 2025-10-19 21:29:47 -06:00
  e61721a0c4
• docs(charts): 📝 write updated reademe
  github-actions[bot] 2025-10-20 03:28:39 +00:00
  2626f04146
• Add dnsConfig and dnsPolicy options (#72)
  Flozza 2025-10-19 21:28:30 -06:00
  29400a65d5
• Merge pull request #65 from FML128/master

  Fix for fresh start with metrix and hostPath option for media

  Tim Eisele 2025-05-01 16:06:28 +02:00
  1b01cffb2d
• docs(charts): 📝 write updated reademe
  github-actions[bot] 2025-05-01 14:06:13 +00:00
  b6ef73e01b
• docs(charts): 📝 write updated reademe
  github-actions[bot] 2025-04-27 22:10:07 +00:00
  2d884535f4
• Fixed README to be consistant with Values
  Merlin Jehli 2025-04-28 00:09:47 +02:00
  d056210a1e
• Added option for media mount to be a hostpath
  Merlin Jehli 2025-04-28 00:09:20 +02:00
  e92576240c
• Fixed init with metrics on
  Merlin Jehli 2025-04-28 00:08:38 +02:00
  54ccfcb5b3
• Update jellyfin/jellyfin Docker tag to v10.10.7
  renovate[bot] 2025-04-05 20:48:32 +00:00
  f82d00dcfa
• docs(charts): 📝 write updated reademe
  github-actions[bot] 2025-03-23 14:31:20 +00:00
  0fcf1d2206
• Add option for priorityClassName (#59)

  Signed-off-by: javex <code@inexplicity.de>

  Flozza 2025-03-23 08:31:01 -06:00
  580d063de4
• docs(charts): 📝 write updated reademe
  github-actions[bot] 2025-03-23 14:30:46 +00:00
  a505e00c4a
• Add option for deployment annotations (#60)
  Jared 2025-03-23 08:30:37 -06:00
  712769f4f8
• docs(charts): 📝 write updated reademe
  github-actions[bot] 2025-03-20 13:11:27 +00:00
  0ab1b10bbd
• chore(jellyfin): Bump chart version to 2.3.0 and set appVersion to 10.10.6
  github-actions[bot] 2025-03-20 13:11:18 +00:00
  14b3b3035b
• fix: 🐛 unify value name and add default (#58)
  Lars 2025-03-20 07:09:09 -06:00
  0e6f86bc8b
• docs(charts): 📝 write updated reademe
  github-actions[bot] 2025-03-19 13:42:30 +00:00
  8a3acbfe46
• chore(jellyfin): Bump chart version to 2.2.0 and set appVersion to 10.10.6
  github-actions[bot] 2025-03-19 13:42:19 +00:00
  8ab1ce45c1
• docs(charts): 📝 write updated reademe
  github-actions[bot] 2025-02-23 17:51:42 +00:00
  9a50e908b0
• chore(chart): ⬆️ bump version
  Supporterino 2025-02-23 18:50:54 +01:00
  d2ccc874ff
• docs(charts): 📝 write updated reademe
  github-actions[bot] 2025-02-23 17:49:34 +00:00
  d6e3d45042
• fix: 🐛 specify port to conform to ServerSideApply
  Supporterino 2025-02-23 18:49:13 +01:00
  2a0b3ae235
• docs(charts): 📝 write updated reademe
  github-actions[bot] 2025-02-17 01:27:04 +00:00
  5487d2a50d
• Update jellyfin/jellyfin Docker tag to v10.10.6 (#52)
  renovate[bot] 2025-02-16 18:26:53 -07:00
  e6a10b0432
• docs(charts): 📝 write updated reademe
  github-actions[bot] 2025-02-09 16:32:31 +00:00
  f9e541b882
• Update jellyfin/jellyfin Docker tag to v10.10.5 (#51)

  Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

  renovate[bot] 2025-02-09 09:32:19 -07:00
  97a05c201b
• docs(charts): 📝 write updated reademe
  github-actions[bot] 2025-02-04 23:54:52 +00:00
  0cffa242a8
• chore: Add metrics warning (#48)

  This adds a small warning about enabling metrics before
  the server has had a chance to configure.

  Sean Johnson 2025-02-04 16:54:44 -07:00
  a20106b1bf