[
https://issues.apache.org/jira/browse/SPARK-24232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472574#comment-16472574
]
Yinan Li commented on SPARK-24232:
----------------------------------
As long as we document it clearly what is for, I think it's OK, particularly
given that `secretKeyRef` is a well-known field name used by k8s.
> Allow referring to kubernetes secrets as env variable
> -----------------------------------------------------
>
> Key: SPARK-24232
> URL: https://issues.apache.org/jira/browse/SPARK-24232
> Project: Spark
> Issue Type: New Feature
> Components: Kubernetes
> Affects Versions: 2.3.0
> Reporter: Dharmesh Kakadia
> Priority: Major
>
> Allow referring to kubernetes secrets in the driver process via environment
> variables. This will allow developers to use secretes without leaking them in
> the code and at the same time secrets can be decoupled and managed
> separately. This can be used to refer to passwords, certificates etc while
> talking to other service (jdbc passwords, storage keys etc).
> So, at the deployment time, something like
> ``spark.kubernetes.driver.secretKeyRef.[EnvName]=<key>`` can be specified
> which will make [EnvName].[key] available as an environment variable and in
> the code its always referred as env variable [key].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
