[
https://issues.apache.org/jira/browse/FLINK-15641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Wang updated FLINK-15641:
------------------------------
Description:
>> 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.
was:
* Sider Container
* Add a sidecar container of FlinkMaster and TaskManager to collector log to
shared storage(hdfs, elastic search, etc.).
* It could also be used for debugging purpose
* Init Container
* Use init container to download users jars dynamically or do something else
before start jobmanager and taskmanager.
> 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)
