Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/23174
> The way it's written now
Code can change after it's written...
> If this change is merged into 3.x without any other changes, users will
be forced to use the K8s secret based
If this change is not merged, users have no way to use authentication at
all. So I don't see your point.
It will prevent you from using the Vault approach in the sense that support
for that won't be implemented yet. But this change, again, does not put a block
on adding support for what you're saying later. If you think that's important
and want to do that in 3.x, then you're free to. But I don't see why this
approach needs to be blocked because it doesn't cover the Vault use case.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
