Github user liyinan926 commented on the issue:
https://github.com/apache/spark/pull/21748
> That is why I suggested also to remove the driver's knowledge of the
driver pod name and to remove the owner reference concept entirely.
While, not worrying about the driver pod name and owner reference doesn't
eliminate the need of a headless service if the driver is indeed running in a
pod. So the question is should the k8s scheduler backend be responsible for
creating the service or not if the driver is running in a pod. I'm personally
leaning towards doing that for the user.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
