[
https://issues.apache.org/jira/browse/FLINK-24944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445615#comment-17445615
]
Yang Wang commented on FLINK-24944:
-----------------------------------
I also believe that using the pod template is enough. Actually, we could not
support all the K8s features(e.g. priority, schedulerName, preemptionPolicy,
dnsPolicy, etc.) via Flink config options. And the pod template is designed to
support those advanced features.
> 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)
