Add Gateway API HTTPRoute support to Helm chart

[lexfrei]

What would you like to be added?

Gateway API HTTPRoute support as an alternative to traditional Ingress for exposing Kubernetes Dashboard.

Why is this needed?

• Gateway API reached GA status (v1.0+, October 2023)
• Provides vendor-neutral, portable ingress configuration
• More flexible routing capabilities compared to Ingress
• Wide adoption by major Gateway controllers (Cilium, Istio, Traefik, Envoy Gateway, Kong Gateway API)
• Modern, role-oriented API design

Gateway API documentation: https://gateway-api.sigs.k8s.io/

Implementation approach

Add HTTPRoute template similar to existing Ingress template:

• Uses Kong proxy service as backend (matching current architecture)
• Configurable via values.yaml
• Compatible with existing Ingress setup (one or the other, not both)
• Support for custom parentRefs, hostnames, and routing rules

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[gurpalw]

/remove-lifecycle stale