Github user echarles commented on the issue:
https://github.com/apache/spark/pull/21748
Got you points. About labels, right, we could take the road of the code
that creates labels on its own pod. To ensure uniqueness, we could use the
`spark-app-id` as key (if it maps the requirement of a label name) and `driver`
as value (let's be imaginative...).
About the permissions, this would have to be documented: I don't see an
issue for a manager to give a pod permission to create services - If security
prohibits this, up to the administrator to create them before hand....
I just feel that we risk to miss some use cases if we don't ship an option
for this (the default behaviour could be the safer with the need to create
manually the service)
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
