<p>I need to capture the TCP packets of my application. I found that sidecar model as explained in <a href="https://developers.redhat.com/blog/2019/02/27/sidecars-analyze-debug-network-traffic-kubernetes-pod/" rel="nofollow noreferrer">sidecars-analyze-debug-network-traffic-kubernetes-pod</a> fits nicely to my application. I would like to know the reasons why something like this should not be done in the production? Basically what are the downside of doing this?</p>

<p>Sure you can run it if convenient for you. Of course additional container will use additional resources in your cluster, but if you can afford it - why not?</p>
<p>Few moments you may be interested in: <a href="https://banzaicloud.com/blog/k8s-sidecars/" rel="nofollow noreferrer">Sidecar container lifecycle changes in Kubernetes 1.18</a></p>
