[
https://issues.apache.org/jira/browse/FLINK-15871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060667#comment-17060667
]
Yang Wang commented on FLINK-15871:
-----------------------------------
If the K8s cluster is multi-tenant and different users want to collect the logs
to their own storage, then you will find the sidecar container is better,
especially for the serverless scenario.
Be careful to add new feature related config option should alway in our mind.
Otherwise, it will flood the config options since the K8s is involving very
fast. I have no preference whether to use the config option or pod template for
the sidecar container.
[~felixzheng] Would you create a ticket for pod template?
> 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)
