You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yang Wang (Jira)" <ji...@apache.org> on 2020/02/01 08:31:00 UTC

[jira] [Commented] (FLINK-15641) Support to start sidecar container and init container

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

Yang Wang commented on FLINK-15641:
-----------------------------------

[~gjy] Thanks for your comments. I think your suggestion to separate this ticket into two different issues makes sense to me.

>> How does sidecar container work?

A sidecar container is running beside the TaskManager container. It could be used to collect log or debug some problems. For example, when we configure the sidecar container to fluentd and share the TaskManager log with volume, then it could be used to upload the logs to HDFS, elastic search, etc. Also we could start a sidecar container with debugging image which contains lots of tools and help to debug the network problems.

 

>> 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.

 

> Support to start sidecar container and 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
>
> * 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)