You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Simon Levett (Jira)" <ji...@apache.org> on 2020/02/10 10:10:00 UTC
[jira] [Commented] (AIRFLOW-5629) Support specify priority and
priorityClassName spec in KubernetesPodOperator
[ https://issues.apache.org/jira/browse/AIRFLOW-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033482#comment-17033482 ]
Simon Levett commented on AIRFLOW-5629:
---------------------------------------
[https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/]
Docs linked only specify setting priorityClassName, and relies exclusively on Priority admission controller to set the numerical value.
I suggest we only set the priorityClassName and not implement the priority (numerical) API?
> Support specify priority and priorityClassName spec in KubernetesPodOperator
> ----------------------------------------------------------------------------
>
> Key: AIRFLOW-5629
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5629
> Project: Apache Airflow
> Issue Type: Improvement
> Components: operators
> Affects Versions: 2.0.0
> Reporter: Yaliang Wang
> Assignee: Yaliang Wang
> Priority: Major
> Labels: features
>
> Since Kubernetes 1.14, Pod can have priority and priority class to indicate the importance of the pod([https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/]). We should support to config the priority and priority class in the KubernetesPodOperator
--
This message was sent by Atlassian Jira
(v8.3.4#803005)