[
https://issues.apache.org/jira/browse/FLINK-15656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076019#comment-17076019
]
Canbin Zheng commented on FLINK-15656:
--------------------------------------
[~fly_in_gis] Sorry for the late reply.
Thanks for the summarization! I think we are in the right direction. We could
continuously listen to the users' feedback and then add necessary Flink side
K8s config options.
Our platform provides the basic images without baking the user jars and lets
the init Container download them into the Containers when deploying per-job
clusters, this init Container is a built-in one which is imperceptible to the
users. So I think such init Container is a basic implementation that should not
be configured via pod template.
Still, people could customize various init Containers according to their
business via pod templates.
> 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)
