[
https://issues.apache.org/jira/browse/SPARK-58160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dongjoon Hyun updated SPARK-58160:
----------------------------------
Parent: SPARK-56825
Issue Type: Sub-task (was: New Feature)
> Add Gateway API HTTPRoute/GRPCRoute support for driver endpoints
> ----------------------------------------------------------------
>
> Key: SPARK-58160
> URL: https://issues.apache.org/jira/browse/SPARK-58160
> Project: Spark
> Issue Type: Sub-task
> Components: Kubernetes
> Affects Versions: kubernetes-operator-1.0.0
> Reporter: Chandni Singh
> Assignee: Chandni Singh
> Priority: Major
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.0.0
>
>
> The Spark Kubernetes Operator currently exposes driver endpoints (Spark UI,
> Spark Connect, etc.) via the `driverServiceIngressList` field, which produces
> a Service and a networking.k8s.io Ingress per entry. Ingress is increasingly
> being replaced by the Kubernetes Gateway API, which is GA for HTTPRoute and
> GRPCRoute v1 and is implemented by all major controllers (Istio, Envoy
> Gateway, Cilium, etc.).
> This ticket proposes adding native, opt-in support for emitting Gateway API
> routes alongside the existing Ingress path, so users moving off ingress-nginx
> (or any Ingress controller) don't have to layer an external route emitter on
> top of the operator.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
