[
https://issues.apache.org/jira/browse/FLINK-24944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445667#comment-17445667
]
liuzhuo commented on FLINK-24944:
---------------------------------
I have an idea to add some functions that can dynamically set parameters on top
of the pod template, such as defining in the pod template:
{code:java}
priorityClassName: ${PriorityClassName}{code}
and then use parameters like `kubernetes.template.env.PriorityClassName` to
dynamically replace the value of `PriorityClassName` of different tasks when
the task is running. so that a unified pod template can be used to run
different Jobs.
> Flink job on k8s mode supports pod scheduling according to priority
> -------------------------------------------------------------------
>
> Key: FLINK-24944
> URL: https://issues.apache.org/jira/browse/FLINK-24944
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Kubernetes
> Reporter: john
> Priority: Major
>
> Hi, is it possible to support the specified pod priority when supporting the
> pod scheduling of the job? I think it is necessary to support the priority
> scheduling of the job in a cluster with multiple users. In Kubernetes 1.8 and
> later versions, the priority of Pod is specified by PriorityClass. At
> present, if I want to specify the priority when submitting a job, I must
> provide a separate pod-templete.yaml for each job, which is often not
> flexible enough. Can we provide a separate parameter similar to
> yarn.application.priority to support the priority of the job when we submit
> the job to k8s,，such as kubernetes .application.priority-class。
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
