We’d like to request support for Kubernetes Gateway API resources in the Console Helm chart, in addition to the current Ingress-based configuration.

In our platform, we are moving away from ingress-nginx due to deprecation/lifecycle constraints, and standardizing on Gateway API-compatible controllers. At the moment, chart exposure appears centered around Ingress, which makes Gateway API adoption difficult without custom out-of-chart manifests.
It would be very helpful if the chart could natively support Gateway API so users can choose either:
• classic Ingress, or
• Gateway API (Gateway + HTTPRoute) for traffic routing.

This would improve compatibility with newer Kubernetes networking setups while preserving backward compatibility for existing Ingress users.