[
https://issues.apache.org/jira/browse/AIRFLOW-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Bandy updated AIRFLOW-3347:
---------------------------------
Description:
We configure Airflow through environment variables. While setting up the
Kubernetes Executor, we wanted to pass the SQL Alchemy connection string to
workers by including it the {{kubernetes_secrets}} section of config.
Unfortunately, even with
{{AIRFLOW_\_KUBERNETES_SECRETS_\_AIRFLOW_\_CORE_\_SQL_ALCHEMY_CONN}} set in the
scheduler environment, the worker gets no environment secret environment
variables.
was:
We configure Airflow through environment variables. While setting up the
Kubernetes Executor, we wanted to pass the SQL Alchemy connection string to
workers by including it the {{kubernetes_secrets}} section of config.
Unfortunately, even with
{{AIRFLOW__KUBERNETES_SECRETS__AIRFLOW__CORE__SQL_ALCHEMY_CONN}} set in the
scheduler environment, the worker gets no environment secret environment
variables.
> Unable to configure Kubernetes secrets through environment
> ----------------------------------------------------------
>
> Key: AIRFLOW-3347
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3347
> Project: Apache Airflow
> Issue Type: Bug
> Components: configuration, kubernetes
> Affects Versions: 1.10.0
> Reporter: Chris Bandy
> Priority: Major
>
> We configure Airflow through environment variables. While setting up the
> Kubernetes Executor, we wanted to pass the SQL Alchemy connection string to
> workers by including it the {{kubernetes_secrets}} section of config.
> Unfortunately, even with
> {{AIRFLOW_\_KUBERNETES_SECRETS_\_AIRFLOW_\_CORE_\_SQL_ALCHEMY_CONN}} set in
> the scheduler environment, the worker gets no environment secret environment
> variables.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
