[
https://issues.apache.org/jira/browse/FLINK-15656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077827#comment-17077827
]
Canbin Zheng commented on FLINK-15656:
--------------------------------------
>> I think it makes sense to me to provide a basic init container to download
>> the user jars and dependencies. At the very beginning, we could leverage the
>> {{FileSystem}} in Flink to support to download from HDFS, S3, OSS, etc.
>> Since [~ouyangwuli] wants to work on this, what do you think about this?
Glad that [~ouyangwuli] would work on the built-in init container
implementation. I could help review the design, code, and test.
>> [~felixzheng] Do you mind to move this ticket as a subtask of FLINK-14460
>> for easier tracking?
Actually I am not very sure that the pod template feature could be merged into
release 1.11.0. Moreover, this ticket needs a design doc and discussion in the
dev mailing list, so I tend to leave it alone instead of being a subtask of
FLINK-14460
> 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)
