spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stavros Kontopoulos (JIRA)" <>
Subject [jira] [Commented] (SPARK-24232) Allow referring to kubernetes secrets as env variable
Date Fri, 11 May 2018 20:08:00 GMT


Stavros Kontopoulos commented on SPARK-24232:

Ok I understand that need for users not to be surprised or break something. A name though
like spark.kubernetes.driver.secretKeyRef.SomeName is not self-explanatory as it does not
add much from a semantics perspective to spark.kubernetes.driver.secrets.SomeName. I know secretKeyRef
is used also in the Pods spec for env secrets, but personally I dont see it really that readable,
but ok for people used to k8s might ring a bell fast ;) . Btw yeah executor secrets need
fix as well.

> Allow referring to kubernetes secrets as env variable
> -----------------------------------------------------
>                 Key: SPARK-24232
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message