Commit Graph
11 Commits
  • Merge upstream/master-vnext into feature/add-inotify-workaround-docs
    Resolve conflicts by combining inotify troubleshooting documentation with
    all features from master-vnext integration branch:
    - inotify troubleshooting docs (this branch)
    - HTTPRoute support
    - envFrom support
    - Startup probe
    - Cache persistence
    - IPv6 dual-stack
    - revisionHistoryLimit
    - initContainers deprecation
    
    Updated version to 3.0.0 and merged all changelog entries.
    Regenerated README.md from template.
    
    Co-Authored-By: Claude <noreply@anthropic.com>
    Signed-off-by: Aleksei Sviridkin <f@lex.la>
  • Merge upstream/master-vnext into feature/add-network-policy
    Resolve conflicts by combining NetworkPolicy feature with all features from
    master-vnext integration branch:
    - NetworkPolicy support (this branch)
    - HTTPRoute support
    - envFrom support
    - Startup probe
    - Cache persistence
    - IPv6 dual-stack
    - revisionHistoryLimit
    - initContainers deprecation
    
    Updated version to 3.0.0 and merged all changelog entries.
    Regenerated README.md from template.
    
    Co-Authored-By: Claude <noreply@anthropic.com>
    Signed-off-by: Aleksei Sviridkin <f@lex.la>
  • 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>
  • docs(troubleshooting): add inotify limits documentation and workaround
    Add comprehensive troubleshooting documentation for inotify instance limit
    errors that cause Jellyfin crashes in environments with many containers.
    
    Changes:
    - Add Troubleshooting section to README with inotify limits explanation
    - Document proper solution: increase kernel limits via sysctl
    - Provide workaround for managed clusters: DOTNET_USE_POLLING_FILE_WATCHER
    - Add commented example in values.yaml for easy copy-paste
    - Update Chart version from 2.5.0 to 2.5.1
    - Add Artifact Hub changelog annotation
    
    The proper solution is to increase inotify limits on Kubernetes nodes:
    ```bash
    sysctl -w fs.inotify.max_user_instances=512
    ```
    
    For managed Kubernetes where node access is restricted, users can use the
    polling workaround (less efficient but functional):
    ```yaml
    jellyfin:
      env:
        - name: DOTNET_USE_POLLING_FILE_WATCHER
          value: "1"
    ```
    
    This addresses the crash issue mentioned in #64.
    
    Fixes: #64
    
    Co-Authored-By: Claude <noreply@anthropic.com>
    Signed-off-by: Aleksei Sviridkin <f@lex.la>
  • fix(ipv6): use httpGet probes by default for IPv4 and IPv6 compatibility
    Change default health probes from tcpSocket to httpGet to fix issue #68
    where pods fail to start in IPv6-only clusters due to incompatible health checks.
    
    Changes:
    - Change default livenessProbe and readinessProbe to use httpGet with /health endpoint
    - Add comprehensive IPv6 and dual-stack configuration documentation
    - Document ipFamilyPolicy options (SingleStack, PreferDualStack, RequireDualStack)
    - Document ipFamilies configuration for IPv4-only, IPv6-only, and dual-stack setups
    - Add IPv6 Configuration section to README with examples
    - Update Chart version from 2.5.0 to 2.5.1
    
    The httpGet probe works with both IPv4 and IPv6 out of the box, while tcpSocket
    may fail in IPv6-only environments. Jellyfin's /health endpoint is specifically
    designed for health checks and verifies both HTTP and database connectivity.
    
    Fixes: #68
    
    Co-Authored-By: Claude <noreply@anthropic.com>
    Signed-off-by: Aleksei Sviridkin <f@lex.la>
  • feat(gateway-api): add HTTPRoute support
    Add support for Kubernetes Gateway API HTTPRoute resource as a modern
    alternative to Ingress. The implementation follows the same pattern as
    the existing Ingress template.
    
    Changes:
    - Add HTTPRoute template with configurable parentRefs, hostnames, and rules
    - Add httpRoute section to values.yaml with generic examples
    - Update Chart version from 2.5.0 to 2.6.0
    - Add Artifact Hub changelog annotation
    - Add HTTPRoute documentation to README
    
    Co-Authored-By: Claude <noreply@anthropic.com>
    Signed-off-by: Aleksei Sviridkin <f@lex.la>
  • chore(docs): 📝 add real URLs and names in READMEs (#38)
    Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>