<p>I'm trying to get my logz.io set up and running and during that process I'm noticing that my ingress controller pod is spitting out a lot of logs. I don't know if its normal or not, but I see a TON of entries in the logs that look like this</p>

<pre><code>[06/Sep/2019:21:27:14 +0000]TCP200004.999
[06/Sep/2019:21:27:17 +0000]TCP200005.000
[06/Sep/2019:21:27:19 +0000]TCP200005.001
[06/Sep/2019:21:27:22 +0000]TCP200004.999
[06/Sep/2019:21:27:24 +0000]TCP200005.001
[06/Sep/2019:21:27:27 +0000]TCP200005.000
.
.
.
</code></pre>

<p>Is this normal? Is my ingress configured wrong? I don't want to see thousands of these entries in my logz.io instance.</p>

Matthew The Terrible
<p>Usually, these logs records reflect <em><a href="https://kubernetes.github.io/ingress-nginx/user-guide/exposing-tcp-udp-services/" rel="nofollow noreferrer">TCP/UDP</a></em> services configuration for upstream backends, when <a href="https://kubernetes.github.io/ingress-nginx/" rel="nofollow noreferrer"><em>Nginx Ingress controller</em></a> applies proxy stream for TCP/UDP connections from relevant <code>ConfigMap</code> by adding specific lua block to the nested  <code>Nginx</code> ingress controller Pod. </p>

<p>Find related discussion in <a href="https://github.com/kubernetes/ingress-nginx/issues/3612" rel="nofollow noreferrer">#3612</a> Github thread.</p>
