[
https://issues.apache.org/jira/browse/FLINK-15641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088439#comment-17088439
]
Yang Wang commented on FLINK-15641:
-----------------------------------
[~ouyangwuli] Thanks a lot for making this ticket moving forward. Just a quick
reminder for the implementation, we could use the Flink {{FileSystem}} to fetch
the jars, artifacts. Then we could support HDFS, S3, Azure, OSS, etc., i think
it is enough for the first version.
It will be great if the init-container implementation could be also used by
standalone perjob cluster.
> Support to start init container
> -------------------------------
>
> Key: FLINK-15641
> URL: https://issues.apache.org/jira/browse/FLINK-15641
> Project: Flink
> Issue Type: New Feature
> Components: Deployment / Kubernetes
> Reporter: Yang Wang
> Priority: Major
>
> >> Why do we need init container?
> The init container could be used to prepare the use jars and dependencies.
> Then we could always set the user image to Flink official image both for
> standalone per-job on K8s or native K8s per-job. When the JobManager and
> TaskManager container launched, the user jars will already exist there. I
> think many users are running standalone per-job cluster in production by
> using this way.
> The init container only works for K8s cluster.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
