[jira] [Resolved] (AIRFLOW-5066) Usage of FieldRef in Kubernetes env execution

["Jarek Potiuk (Jira)" <ji...@apache.org>]

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

Jarek Potiuk resolved AIRFLOW-5066.
-----------------------------------
    Fix Version/s: 1.10.7
       Resolution: Fixed

> Usage of FieldRef in Kubernetes env execution
> ---------------------------------------------
>
>                 Key: AIRFLOW-5066
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-5066
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: executors
>    Affects Versions: 1.10.4, 2.0.0, 1.10.5
>            Reporter: Julien Surloppe
>            Priority: Minor
>             Fix For: 1.10.7
>
>
> In Kubernetes, dynamic pod metadata can be set as environment variables and then used as substitution in other environment variables.
> Currently in Airflow, the pod request creation set those variables after the ones that can use substitutions so them doen't do it.
> Example usage is:
>  * define a variable SPARK_LOCAL_IP using the pod metadata status.podIP
>  * using this variable in Spark options as -Dspark.driver.host=$(SPARK_LOCAL_IP)
> I will do a PR to fix this behavior.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)