Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.3.0
-
None
Description
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].
