We are moving away from ingress-nginx to the Kubernetes Gateway API, and we're using the Spark Kubernetes Operator to launch Spark workloads. It would be great if the operator could natively emit Gateway API routes (HTTPRoute / GRPCRoute) for driver endpoints like the Spark UI and Spark Connect, alongside the existing driverServiceIngressList Ingress path.
The shape I have in mind is opt-in and parallel to the existing Ingress field - no behavior change when unset. Other Gateway API implementations (Istio, Envoy Gateway, Cilium) are GA on HTTPRoute / GRPCRoute v1, so this will not be tied to a specific controller. If there are no objections, I'll file a Spark JIRA and start working on a patch. Thank you, Chandni
