Yang Jie created SPARK-59053:
--------------------------------
Summary: Warn when the executor pod template's service account
drops the configured one
Key: SPARK-59053
URL: https://issues.apache.org/jira/browse/SPARK-59053
Project: Spark
Issue Type: Improvement
Components: Kubernetes
Affects Versions: 5.0.0
Reporter: Yang Jie
`ExecutorKubernetesCredentialsFeatureStep` applies
`spark.kubernetes.authenticate.executor.serviceAccountName`, falling back to
the value of `spark.kubernetes.authenticate.driver.serviceAccountName`, only
when the executor pod template names no service account. When the template does
name one, the configured account is discarded and nothing is written to the log
-- the step does not even mix in `Logging`.
SPARK-58872 added a WARN for the analogous situation on the driver side, where
submitted driver credentials take precedence over
`spark.kubernetes.authenticate.driver.serviceAccountName`, and documented it in
`running-on-kubernetes.md`. The two are not the same code path, but the user
sees the same thing: a service account configuration that is set, does not
apply, and says nothing about why.
Follow-up to SPARK-58910, which fixed the guard that decides whether the
template names an account. That fix is a bug fix headed for the maintenance
branches, so adding the warning there would carry an improvement onto branches
it does not belong on.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
