You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Chengzhi Zhao (JIRA)" <ji...@apache.org> on 2019/02/20 19:36:00 UTC
[jira] [Created] (AIRFLOW-3930) Add namespace as part of
KubernetesExecutorConfig
Chengzhi Zhao created AIRFLOW-3930:
--------------------------------------
Summary: Add namespace as part of KubernetesExecutorConfig
Key: AIRFLOW-3930
URL: https://issues.apache.org/jira/browse/AIRFLOW-3930
Project: Apache Airflow
Issue Type: New Feature
Components: kubernetes
Affects Versions: 1.10.2
Reporter: Chengzhi Zhao
Currently, there is no option for the user to select which namespace each task can run, all default to one namespace. If we want to use Kubernetes `limit range` on the different namespace, it is very hard to do since all pod will be launch on the namespace defined in config.cfg.
For example, if Task A limits to only 200M memory but Task B limits to 2G, it would be nice to run Task A under one namespace with limit 200M and Task B under another namespace with limit 2G.
I think it is also very helpful to manage tasks by namespaces as well.
Please share your thoughts if this is some use cases you would consider.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)