3 Commits

Include renames

• fix(charts): add automountServiceAccountToken and fix schema validations

  - Add automountServiceAccountToken to deployment.yaml template (was missing)
  - Fix image.repository pattern in schema to allow registry with port (e.g., registry.example.com:5000)
  - Add ExternalName to service.type enum in schema
  - Remove ExternalName tests from service_test.yaml and validation_mutual_exclusions_test.yaml (not implemented in template)
  - Fix integration test: change persistence.media.type from 'nfs' to 'hostPath' (nfs not supported)
  
  These fixes address test failures related to schema validation and missing template fields.
  
  Co-Authored-By: Claude <noreply@anthropic.com>
  Signed-off-by: Aleksei Sviridkin <f@lex.la>

  Aleksei SviridkinandClaude 2025-11-08 17:43:02 +03:00
  7e2690d3c4
• refactor(schema): comprehensive validation with enums, patterns, and detailed documentation

  Significantly improve values.schema.json:
  
  - Add enums for all constrained values (pullPolicy, service.type, dnsPolicy,
    deploymentStrategy, ipFamilyPolicy, pathType, persistence.type, accessMode)
  - Add regex patterns for Kubernetes-specific formats (size, CIDR, intervals)
  - Add port range validation (1-65535, nodePort 30000-32767)
  - Add hostname format validation for Ingress/HTTPRoute
  - Add required fields for arrays (env.name, imagePullSecrets.name)
  - Add detailed structure for envFrom, env, imagePullSecrets
  - Add comprehensive descriptions for every field with defaults and examples
  - Add uniqueItems, minItems, maxItems constraints where applicable
  
  Validated against:
  - Invalid size patterns (rejects non-Kubernetes formats)
  - Invalid enums (rejects 'nfs' for persistence.type)
  - Invalid CIDR notation (IPv4/IPv6 regex)
  - Mutual exclusivity (NetworkPolicy vs hostNetwork/DLNA)
  
  Co-Authored-By: Claude <noreply@anthropic.com>
  Signed-off-by: Aleksei Sviridkin <f@lex.la>

  Aleksei SviridkinandClaude 2025-11-08 16:27:49 +03:00
  29d292e5f8
• feat(chart): add JSON Schema with NetworkPolicy/hostNetwork conflict validation

  Add values.schema.json with comprehensive validation for chart values:
  - All core fields with types, defaults, and enums
  - Validation preventing NetworkPolicy + hostNetwork conflicts
  - Validation preventing NetworkPolicy + DLNA conflicts
  
  The schema uses JSON Schema draft-07 with allOf/if-then logic to enforce
  mutual exclusivity: networkPolicy.enabled cannot be true when either
  jellyfin.enableDLNA or podPrivileges.hostNetwork is true.
  
  Validated with check-jsonschema against current values.yaml and
  test cases for both valid and invalid configurations.
  
  Co-Authored-By: Claude <noreply@anthropic.com>
  Signed-off-by: Aleksei Sviridkin <f@lex.la>

  Aleksei SviridkinandClaude 2025-11-08 16:21:37 +03:00
  f9d897c321