[
https://issues.apache.org/jira/browse/AIRFLOW-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585772#comment-16585772
]
Jon Davies commented on AIRFLOW-2920:
-------------------------------------
Probably need to use this to expose the namespace to the pods:
https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/user-guide/downward-api.md
> Kubernetes pod operator: namespace is a hard requirement
> --------------------------------------------------------
>
> Key: AIRFLOW-2920
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2920
> Project: Apache Airflow
> Issue Type: Bug
> Reporter: Jon Davies
> Priority: Major
>
> Hello,
> I'm using the Kubernetes pod operator for my DAGs, I install Airflow to its
> own namespace within my Kubernetes cluster (for example: "testing-airflow")
> and I would like pods spun up by that Airflow instance to live in that
> namespace.
> However, I have to hardcode the namespace into my DAG definition code and so
> I have to rebuild the Docker image for Airflow to be able to spin up a
> "production-airflow" namespace as the namespace is a hard requirement in the
> Python code - it'd be nice if the DAG could just default to its own namespace
> if none is defined.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
