[
https://issues.apache.org/jira/browse/FLINK-15871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060860#comment-17060860
]
Canbin Zheng commented on FLINK-15871:
--------------------------------------
Hi, [~ouyangwuli]!
In our internal version, we use init containers for the per job cluster to
resolve dynamic dependencies such as downing the user jars, job graph file,
etc. The init container support is a basic design which is not customized by
the end users so far.
I am not sure what's your previous plan on the functionality of the init
containers, could you share more information?
> Support to start sidecar container
> ----------------------------------
>
> Key: FLINK-15871
> URL: https://issues.apache.org/jira/browse/FLINK-15871
> Project: Flink
> Issue Type: Sub-task
> Components: Deployment / Kubernetes
> Affects Versions: 1.10.0
> Reporter: Yang Wang
> Priority: Major
> Fix For: 1.11.0
>
>
> >> How does sidecar container work?
> A sidecar container is running beside the Jobmanager and 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
