[
https://issues.apache.org/jira/browse/FLINK-15656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071505#comment-17071505
]
Yang Wang edited comment on FLINK-15656 at 3/31/20, 7:19 AM:
-------------------------------------------------------------
[~felixzheng] [~ouyangwuli]
I am trying to rethink the necessity of init-container and sidecar container.
Recently, i have asked our internal and cloud users how they would like to run
perjob cluster. And i get such outputs.
* Many of them prefer to build their own docker image for perjob cluster.
Because it is faster to launch.
* Others want to use init container via flink config options. They have
various requirements, not only to download the user jar, but also to do some
their own external service check. So it will be hard to support such common use
case.
* Some other users prefer to use the pod template. It is flexible enough so
that they could customize their own pre-check and initialization logics.
* The platform developers also prefer pod template.
I want to share the information with you and maybe your users have different
requirements. All in all, i think we need to raise the priority of this ticket
and hope to get merged in 1.11.
was (Author: fly_in_gis):
[~felixzheng] [~ouyangwuli]
I am trying to rethink the necessity of init-container and sidecar container.
Recently, i have asked our internal and cloud users how they would like to run
perjob cluster. And i get such output
It seems that many of them prefer build their own docker image for perjob
cluster. Because using init container
> Support user-specified pod templates
> ------------------------------------
>
> Key: FLINK-15656
> URL: https://issues.apache.org/jira/browse/FLINK-15656
> Project: Flink
> Issue Type: New Feature
> Components: Deployment / Kubernetes
> Reporter: Canbin Zheng
> Priority: Major
>
> The current approach of introducing new configuration options for each aspect
> of pod specification a user might wish is becoming unwieldy, we have to
> maintain more and more Flink side Kubernetes configuration options and users
> have to learn the gap between the declarative model used by Kubernetes and
> the configuration model used by Flink. It's a great improvement to allow
> users to specify pod templates as central places for all customization needs
> for the jobmanager and taskmanager pods.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
