[
https://issues.apache.org/jira/browse/FLINK-15871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060740#comment-17060740
]
Yang Wang commented on FLINK-15871:
-----------------------------------
Though i do not insist with adding explicit config options for sidecar, mostly
because not only one sidecar container may need to start and usually we need to
configure entrypoint, cmd, etc., i want to say that using the sidecar container
for log-collecting is not a rare use case.
Many users do not want to expose the credentials to the daemon set log
collector. It is not safe, so they choose sidecar container to collect the logs
to their own storage(S3, Aliyun OSS, etc.).
> 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)
