You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Sam Danbury (JIRA)" <ji...@apache.org> on 2019/08/12 13:25:00 UTC
[jira] [Updated] (AIRFLOW-5173) Pass worker pod resource limits and
requests from airflow config for KubernetesExecutor
[ https://issues.apache.org/jira/browse/AIRFLOW-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sam Danbury updated AIRFLOW-5173:
---------------------------------
Description:
It is possible to send in resource limits and requests as part of the executor_config argument at a task/operator level. However, there is not currently a way to pass config in at the executor level to apply a default resource configuration for all KubernetesExecutor worker pods.
The entire pod spec is not currently supported at an airflow.cfg level, which is a larger task. This issue is specifically for the resource limits and requests part of the spec.
was:
It is possible to send in resource limits and requests as part of the `executor_config` argument at a task/operator level. However, there is not currently a way to pass config in at the executor level to apply a default resource configuration for all KubernetesExecutor worker pods.
The entire pod spec is not currently supported at an airflow.cfg level, which is a larger task. This issue is specifically for the resource limits and requests part of the spec.
> Pass worker pod resource limits and requests from airflow config for KubernetesExecutor
> ---------------------------------------------------------------------------------------
>
> Key: AIRFLOW-5173
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5173
> Project: Apache Airflow
> Issue Type: Improvement
> Components: configuration
> Affects Versions: 1.10.4
> Reporter: Sam Danbury
> Priority: Minor
> Labels: kubernetes, pull-request-available
>
> It is possible to send in resource limits and requests as part of the executor_config argument at a task/operator level. However, there is not currently a way to pass config in at the executor level to apply a default resource configuration for all KubernetesExecutor worker pods.
>
> The entire pod spec is not currently supported at an airflow.cfg level, which is a larger task. This issue is specifically for the resource limits and requests part of the spec.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)