[
https://issues.apache.org/jira/browse/SPARK-58160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18096659#comment-18096659
]
Dongjoon Hyun commented on SPARK-58160:
---------------------------------------
According to the Apache Spark contribution guideline,
https://spark.apache.org/contributing.html, feel free to make a PR with this
JIRA ID, [~csingh]. We eliminate the burden of assignments. When the PR is
merged by the committers, the committer assigns the PR author to the JIRA issue
as the `Assignee`. Fix Version field is also determined at the merging time.
> There is no need to be the Assignee of the JIRA to work on it, though you are
> welcome to comment that you have begun work.
> 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: New Feature
> Components: Kubernetes
> Affects Versions: 0.9.2
> Reporter: Chandni Singh
> Priority: Major
>
> 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]
