Github user rvesse commented on the issue:
https://github.com/apache/spark/pull/23013
@mccheah I have tried to keep it minimal and just point to the official K8S
docs. Obviously there is a balance to be had between high level warnings and
detailed advice. K8S is still a relatively new technology to the wider
industry regardless of its maturity as a whole so we should be highlighting the
obvious pitfalls.
@tgravescs
1. K8S API defaults to SSL by default, primarily the Fabric 8 library
auto-configures itself from the users K8S config file which will typically set
up all the necessary authentication. All the various authentication properties
are used to override that initial auto-configuration and are unnecessary for
most users.
2. Not sure
3. I haven't used client mode much so can't comment
4. Kerberos is already covered in more details in the main security doc
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
