Gateway API support

[gimmw]

Probably not high on the priority list, but could operator support for Gateway API HTTPRoutes (additional to Ingress) be considered?

While Ingress isn't going anywhere any time soon, Gateway API is the emerging standard to which all future efforts will be directed.

In my no-ingress cluster, currently I'm just adding an additional HTTPRoute for each ShinyProxy instance and that works fine. Basically just something like

---
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: sp-foo-httproute
  namespace: shinyproxy
spec:
  parentRefs:
  - name: my-gw
    namespace: gateways
  hostnames:
  - shiny.bar.blah
  rules:
    - matches:
      - path:
          type: PathPrefix
          value: /foo
      backendRefs:
        - name: sp-foo-svc
          port: 80

[LEDfan]

Hi

In our experience we currently only see clusters that still have support for the ingress resource. Therefore, as you mention, we don't see a big need to support the Gateway API.
However, at some point we'll probably have to support it, so I'm going to keep this open as a feature request.
If other finds this useful, please vote on this issue!

[LEDfan]

With the deprecation of ingress-nginx, we see more users moving to Gateway API only. Therefore, we are prioritizing this more and will probably include this in the next release.