You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Philippe Gagnon (JIRA)" <ji...@apache.org> on 2019/05/28 15:30:00 UTC
[jira] [Commented] (AIRFLOW-4582) Set KubernetesExecutor worker pod
limits and requests based on "resources" task attribute
[ https://issues.apache.org/jira/browse/AIRFLOW-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849847#comment-16849847 ]
Philippe Gagnon commented on AIRFLOW-4582:
------------------------------------------
@[~dimberman] What do you think? I'll implement this if you are on-board.
> 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: executor
> Affects Versions: 1.10.3
> Reporter: Philippe Gagnon
> Assignee: Philippe Gagnon
> Priority: Major
> Labels: Kubernetes, executor
> Fix For: 1.10.4
>
>
> 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)