Support for httproutes and gatewayapi

[m-castaldo]

Describe the feature request

We would like native support for exposing Unleash Edge via the Kubernetes Gateway API (HTTPRoute) in addition to the current Ingress-based configuration.

Specifically, the Helm chart should support:

Optional creation of HTTPRoute resources
Configurable parentRefs to attach to an existing Gateway
Hostname configuration
Path matching configuration
TLS support (via Gateway)
Ability to disable traditional Ingress when Gateway API is enabled

This would allow Unleash Edge to integrate cleanly with modern Kubernetes networking setups that use Gateway API instead of Ingress.

Background

Many Kubernetes environments are moving toward Gateway API as the standard for traffic management. In clusters where Ingress is no longer used (or restricted), it becomes difficult to expose Unleash Edge cleanly without writing additional manifests outside the Helm chart.

Native support would:

Improve compatibility with modern Kubernetes clusters
Simplify GitOps workflows
Avoid the need for separate custom HTTPRoute manifests
Align Unleash Edge with current Kubernetes networking best practices

Solution suggestions

gatewayApi:
  enabled: true
  namespace: unleash
  parentRefs:
    - name: avi-gateway
      namespace: avi-system
  hostnames:
    - unleash-edge.example.com
  rules:
    - matches:
        - path:
            type: PathPrefix
            value: /
      backendRefs:
        - name: unleash-edge
          port: 80

When gatewayApi.enabled=true, the chart would:

Create an HTTPRoute
Attach it to the specified Gateway
Disable Ingress creation automatically (or allow explicit override)

[chriswk]

Hi @m-castaldo - we don't currently have capacity to add this feature, but I do have capacity to review a PR, so if this is urgent. I would file a PR