Add HTTPRoute Support for Gateway API (nginx-ingress Retirement)

[bashao]

Hi team,

As part of our Kubernetes ingress migration efforts, we’d like to request adding HTTPRoute support to the Retool Helm chart in order to enable ingress via the Gateway API.

The nginx-ingress controller is being retired at the end of March, and many clusters (including ours) are transitioning away from Ingress resources toward the Gateway API standard. Currently, the Retool Helm chart supports only the traditional Ingress resource, which limits our ability to adopt Gateway-based routing.

To ensure continued production compatibility and to align with modern Kubernetes networking patterns, we would greatly appreciate support for:

• Generating an HTTPRoute resource alongside or instead of the existing Ingress object
• Exposing configuration options in values.yaml similar to the current ingress settings
• Allowing selection of parent Gateway and configuring hostnames, rules, and backend references

Adding this capability will allow users to seamlessly route traffic to Retool through Gateway API implementations such as GKE Gateway Controller, Istio, Envoy Gateway, and others.

Please let me know if you'd like assistance drafting a proposed schema for values or contributing a PR.

Thanks!