[
https://issues.apache.org/jira/browse/FLINK-15871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060649#comment-17060649
]
ouyangwulin commented on FLINK-15871:
-------------------------------------
[~felixzheng]
> As collect logs, I think have two method, one is use sidecar, the other is
>use deamonset. But I don't think deamonset is a good idea for flink project,
>Beacause It need user logs to the pods's console. So in our env, we still use
>sidecar for collect log. we don't think sidecar is consume too many resources,
>but it is more flexible.
> 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)
