The Kubernetes Gateway API has reached GA (General Availability) and is becoming the standard successor to the Ingress API. Currently, the Trino Helm chart only supports generating Ingress resources via the ingress.enabled block.
As clusters migrate away from Ingress controllers (like NGINX Ingress) toward Gateway API implementations (like Istio, Cilium, or Gateway API for NGINX), users are forced to manage their Trino routing configuration outside of this Helm chart. This breaks the encapsulation of the Helm release, requiring us to disable ingress in values.yaml and manually maintain separate HTTPRoute manifests to expose the Trino service.