[
https://issues.apache.org/jira/browse/SPARK-24232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470333#comment-16470333
]
Stavros Kontopoulos edited comment on SPARK-24232 at 5/10/18 12:43 PM:
-----------------------------------------------------------------------
Check also what we use on mesos for naming conventions for env secrets:
[https://spark.apache.org/docs/latest/running-on-mesos.html]
I will give it a shot seems straightforward to add. Any reason why this
shouldn't be added?
was (Author: skonto):
Check also what we use on mesos for naming conventions for env secrets:
[https://spark.apache.org/docs/latest/running-on-mesos.html]
Might work on this seems straightforward to add.
> 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: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
