Migrate Helm charts to new `helm create` structure with Gateway API support

[michaelbeutler]

The Kubernetes Ingress NGINX project is no longer expected to be maintained after March 2026. To ensure forward compatibility and align with Kubernetes networking direction, we must support Gateway API across all Helm charts in this repository.

Currently, charts in truvami/helm do not follow the latest helm create structure and do not include Gateway API templates. This issue tracks the work required to migrate all charts to the modern Helm chart layout and add first-class Gateway API support while maintaining backward compatibility where required.

Objectives:

• Migrate all existing charts to the current helm create scaffold
• Introduce Gateway API templates alongside existing ingress support
• Standardize values and templates across charts
• Minimize breaking changes for existing consumers

Scope of Work:

1. Helm Chart Structure

   • Recreate charts using the latest helm create output as a baseline
   • Ensure consistent directory layout, helpers, and metadata
   • Normalize naming conventions and labels

2. Gateway API Support

   • Add templates for:
     • Gateway
     • HTTPRoute (and others if required later)
   • Introduce values under a new gateway (or gatewayAPI) section, e.g.:

     gateway:
       enabled: false
       gatewayClassName: ""
       hostnames: []
       listeners: []

   • Support routing configuration equivalent to current ingress functionality

3. Ingress Compatibility

   • Retain existing Ingress templates behind a feature flag (e.g. ingress.enabled)
   • Ensure Gateway API and Ingress are mutually exclusive or clearly prioritized

4. Values & Documentation

   • Update values.yaml with clear defaults and comments
   • Document Gateway API usage in each chart’s README
   • Provide migration guidance from Ingress → Gateway API

5. Testing & Validation

   • Run helm lint on all updated charts

   • Validate rendered manifests for:

     • Ingress-only
     • Gateway API–only
     • Neither enabled (where applicable)

Acceptance Criteria:

• All charts conform to the current helm create structure
• Gateway API can be enabled via values without custom templating
• Existing Ingress-based deployments continue to work unchanged
• Documentation clearly explains configuration and migration paths

Notes / References:

• Gateway API: https://gateway-api.sigs.k8s.io/
• Helm chart best practices: https://helm.sh/docs/chart_best_practices/