[
https://issues.apache.org/jira/browse/FLINK-15641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060654#comment-17060654
]
ouyangwulin edited comment on FLINK-15641 at 3/17/20, 6:00 AM:
---------------------------------------------------------------
[~fly_in_gis] As flink on k8s ,not native. I think init container has another
Scenario, that when before the tm start ,It use to probe the jm pod have
started。
and flink native on k8s, the tm pod start after the jm pod started. So it don't
need the probe.
was (Author: ouyangwuli):
[~fly_in_gis] As flink on k8s ,not native. I think init container has another
Scenario, that when before the tm start ,It use to probe the jm pod have
started。
> 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)
