Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/21669
> The clusters Kerberos config file pointed the KDC to an IP not visible to
my K8S pod
In the case where the launcher is fetching delegation tokens and providing
them to the driver, is there even any need for the driver to talk to the KDC?
In that case you probably don't even need the krb5.conf file mounted on the
driver (or executors) at all.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
