[
https://issues.apache.org/jira/browse/AIRFLOW-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ash Berlin-Taylor updated AIRFLOW-4582:
---------------------------------------
Fix Version/s: (was: 1.10.4)
This sounds sensible to me (and I think probably surprising to people that it
doesn't work already)
> Set KubernetesExecutor worker pod limits and requests based on "resources"
> task attribute
> -----------------------------------------------------------------------------------------
>
> Key: AIRFLOW-4582
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4582
> Project: Apache Airflow
> Issue Type: Improvement
> Components: executors
> Affects Versions: 1.10.3
> Reporter: Philippe Gagnon
> Assignee: Philippe Gagnon
> Priority: Major
> Labels: Kubernetes, executor
>
> At this time the {{KubernetesExecutor}} does not honor resource limits or
> requests set in the {{resources}} task attribute.
> It is possible to set limits and requests by passing an {{executor_config}}
> dict, however this method seems sub-optimal, considering that a generic
> built-in task attribute with essentially the same purpose is already
> available.
> I think we should implement this functionality, but gate it behind an opt-in
> configuration parameter to ensure backwards-compatibility.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
