<p>I see some strange logs in my kong container, which internally uses nginx:</p>

<pre><code>2019/08/07 15:54:18 [info] 32#0: *96775 client closed connection while SSL handshaking, client: 10.244.0.1, server: 0.0.0.0:8443
</code></pre>

<p>This happens every 5 secs, like some sort of diagnostic is on.
In my kubernetes descriptor I set no ready or liveliness probe, so I can't understand why there  are those calls and how can I prevent them from appearing as they only dirt my logs...</p>

<p><strong>edit</strong>: 
It seems it's the LoadBalancer service: I tried deleting it and I get no logs anymore...how to get rid of those logs though?</p>

<p>This has been already discussed on Kong forum in <a href="https://discuss.konghq.com/t/stopping-logs-generated-by-the-aws-elb-health-check/3752" rel="nofollow noreferrer">Stopping logs generated by the AWS ELB health check</a> thread.
The same behaviour with lb heathcheck every few seconds.</p>
<blockquote>
<p>Make Kong listen on plain HTTP port, open that port up only to the
subnet in which ELB is running (public most probably), and then don’t
open up port 80 on the ELB. So ELB will be able to Talk on port 80 for
health-check but there won’t be a HTTP port available to external
world.</p>
<p>Use L4 proxying (stream_listen) in kong, open up the port and
then make ELB healthcheck that port.</p>
</blockquote>
<p>Both of solutions are reasonable.</p>
