[jira] [Comment Edited] (FLINK-15641) Support to start init container

["Canbin Zheng (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-15641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029510#comment-17029510 ] 

Canbin Zheng edited comment on FLINK-15641 at 2/4/20 3:05 AM:
--------------------------------------------------------------

Hi [~fly_in_gis], it seems that the init-container work could be included in Support per-job mode in kubernetes ?


was (Author: felixzheng):
Hi [~fly_in_gis], It seems that the init-container work could be included in Support per-job mode in kubernetes ?

> Support to start init container
> -------------------------------
>
>                 Key: FLINK-15641
>                 URL: https://issues.apache.org/jira/browse/FLINK-15641
>             Project: Flink
>          Issue Type: Sub-task
>          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)