You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Julien Surloppe (JIRA)" <ji...@apache.org> on 2019/07/29 10:12:00 UTC

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

Julien Surloppe created AIRFLOW-5066:
----------------------------------------

             Summary: 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


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
(v7.6.14#76016)