[ 
https://issues.apache.org/jira/browse/SPARK-56275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dongjoon Hyun resolved SPARK-56275.
-----------------------------------
    Fix Version/s: 4.2.0
       Resolution: Fixed

Issue resolved by pull request 55148
[https://github.com/apache/spark/pull/55148]

> Set appProtocol on spark-connect service port
> ---------------------------------------------
>
>                 Key: SPARK-56275
>                 URL: https://issues.apache.org/jira/browse/SPARK-56275
>             Project: Spark
>          Issue Type: Improvement
>          Components: Kubernetes
>    Affects Versions: kubernetes-operator-0.9.0
>            Reporter: Jiwon Park
>            Assignee: Jiwon Park
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 4.2.0
>
>
> Set appProtocol to "grpc" on the spark-connect port in 
> DriverServiceFeatureStep.
> Without appProtocol, service meshes (e.g. Istio, Linkerd) treat gRPC traffic 
> as opaque TCP, which prevents L7-aware load balancing and gRPC health 
> checking for Spark Connect sessions.
> This change is limited to the spark-connect port because gRPC is unambiguous 
> regardless of SSL configuration. Other ports (HTTP-based) are left untouched 
> since their protocol depends on spark.ssl.* settings.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to