[
https://issues.apache.org/jira/browse/FLINK-15656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17078853#comment-17078853
]
Canbin Zheng commented on FLINK-15656:
--------------------------------------
[~ouyangwuli], [~fly_in_gis] The built-in init Container is imperceptible to
the users, right? So, I am thinking about how people use it?
I described the internal case that we use init Container only for the K8s
per-job mode to download job graph file, user jars into the Container, that's
all the functionality it provides. It is not a user-faced functionality so that
people could not configure it to download other dependencies.
Besides, I do not have read permission to the doc, [~ouyangwuli]
https://docs.google.com/document/d/1CtPgW0_a4HyF7tN-KVDyoNj43wDn-ZZVdXYS17Sz2rw/edit
> 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)
