[
https://issues.apache.org/jira/browse/FLINK-15871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060691#comment-17060691
]
Canbin Zheng commented on FLINK-15871:
--------------------------------------
{color:#0e101a}Hi {color}[{color:#4a6ee0}Yang
Wang{color}|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=fly_in_gis]{color:#0e101a}!{color}
{color:#0e101a}> 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. {color}
{color:#0e101a}I would like to share some information{color}
# {color:#0e101a}The K8s products(serverless or non-serverless) in the Cloud
environment usually provide several solutions to collect logs to Kafka, ES,
etc; users are not necessary to deploy their collector service. Of course, the
solutions support multi-tenant.{color}
# {color:#0e101a}For the self-built K8s cluster, usually, we advise the users
to collect logs via log-proxy deployed on the host instead of introducing the
sidecar containers.{color}
# {color:#0e101a}Indeed, it's possible that a small proportion of users would
use the customized sidecar container for some reason, but seems this is not the
most common scenario.{color}
{color:#0e101a}Therefore, I think the sidecar container is somewhat an advanced
feature instead of a basic one, moreover, FLINK-15656 could support this
feature.{color}
{color:#0e101a}> Would you create a ticket for pod template?{color}
{color:#0e101a}I have created
[FLINK-15656|https://issues.apache.org/jira/browse/FLINK-15656] to track this
feature before.{color}
{color:#0e101a} {color}
> 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)