[jira] [Updated] (AIRFLOW-3258) Add ability to set Environment Variables for pods brought up by Kubernetes Executor

["Aizhamal Nurmamat kyzy (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AIRFLOW-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aizhamal Nurmamat kyzy updated AIRFLOW-3258:
--------------------------------------------
    Component/s:     (was: kubernetes)
                 operators

Moving to operators component, and labeling with kubernetes as part of the component refactor.

> 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: operators
>    Affects Versions: 1.10.0
>            Reporter: David Lum
>            Assignee: David Lum
>            Priority: Minor
>              Labels: kubernetes
>             Fix For: 1.10.3
>
>
> 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)