Commit Graph
2 Commits
  • test(service): add IPv6 and dual-stack configuration tests
    Add helm-unittest tests for IPv6 and dual-stack Service configuration:
    - Default behavior (no ipFamilyPolicy/ipFamilies set)
    - SingleStack, PreferDualStack, RequireDualStack policies
    - IPv4 only, IPv6 only configurations
    - Dual-stack with IPv4 primary and IPv6 primary
    - Combined policy and families configurations
    
    Add NOTES.txt with IPv6/dual-stack information:
    - Display configured IP family policy
    - Show IP families list
    - Warning when IPv6 is primary (probe compatibility note)
    - Warning when IPv6 used without policy
    
    Tests ensure IPv6 and dual-stack work correctly for all scenarios.
    
    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>