[
https://issues.apache.org/jira/browse/AIRFLOW-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16785915#comment-16785915
]
ASF subversion and git services commented on AIRFLOW-3258:
----------------------------------------------------------
Commit 0c4774d605a2786bbf44fb6f5bed15addadeb5e7 in airflow's branch
refs/heads/master from davlum
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=0c4774d ]
[AIRFLOW-3258] K8S executor environment variables section. (#4627)
* [AIRFLOW-3258] K8S executor, optional mount current env in worker pods
* fix(AIRFLOW-3258): fix tests
* fetch config in KubeConfig init
* fix(AIRFLOW-3258): address pr comments
feat(AIRFLOW-3258): move feature to AIRFLOW-4008
fix(AIRFLOW-3258): fix tests
* refactor(AIRFLOW-3258): changes for PR
> Add ability to set Environment Variables for pods brought up by Kubernetes
> Executor
> -----------------------------------------------------------------------------------
>
> Key: AIRFLOW-3258
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3258
> Project: Apache Airflow
> Issue Type: Improvement
> Components: kubernetes
> Affects Versions: 1.10.0
> Reporter: David Lum
> Assignee: David Lum
> Priority: Minor
> Labels: kubernetes
> Fix For: 1.10.0
>
>
> Currently the only way to add arbitrary environment variables to pods brought
> up by the KubernetesExecutor is to add them using Kubernetes secrets, and
> then specifying those secrets in the in the kubernetes_secrets section of the
> the airflow.cfg. However, not all environment variables are secrets and need
> to be encoded. The suggestion would be to add another section to the
> airflow.cfg, kubernetes_environment_variables.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
