Github user mccheah commented on the issue:
https://github.com/apache/spark/pull/21748
> Yes, the service gets its endpoints by matching its label selector
against labels on the pods so it's critical to have matching labels. Another
tenable solution is for the driver backend code to get the pod object of the
driver and sets the label selector of the service based on the labels on the
driver pod.
The problem is that the driver's labels might not be unique to that driver,
which therefore would require the user to assign their own unique labels or for
us to patch the driver pod in-place to assign it a unique label. Neither seem
ideal.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
