Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/23174
> A proposed scheme is to have
spark.authenticate.k8s.secret.provider=autok8ssecret
If you're going to add a different way to get the auth secret later, then
you can introduce that option with a default value. It does not mean it needs
to be done *in this change*, which is my point.
The only real change being introduced here form the Spark status quo is
that you don't need to provide your own auth secret in the configuration (i.e.
it would work like YARN), which doesn't even work in k8s today because that is
not propagated to the executors in any way. And if you think that is a problem
I can gate the generation of the secret based on whether one is already defined
in the config.
> if it's not introduced in this patch, then at least we should file JIRA
tickets
That is fine with me.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
