Bug 1820577

Description of problem:
In Azure cloud cluster, EVEN in fresh env without any user operation, KAS pod logs spam with many "http: TLS handshake error from 168.63.129.16:<port>: EOF"

Version-Release number of selected component (if applicable):
4.4.0-0.nightly-2020-04-02-130551

How reproducible:
Always

Steps to Reproduce:
1. Launch fresh Azure IPI env successfully.
2. Without any user operation, check KAS pod logs
$ oc logs -n openshift-kube-apiserver -c kube-apiserver kube-apiserver-xxia1-0403-tkfs8-master-0 --tail 1 -f

Actual results:
2. EVEN in fresh env given NO any user operation, the logs spam frequently with many below errors:
I0403 10:27:08.835307       1 log.go:172] http: TLS handshake error from 168.63.129.16:55477: EOF
I0403 10:27:18.851322       1 log.go:172] http: TLS handshake error from 168.63.129.16:55548: EOF
I0403 10:27:28.866113       1 log.go:172] http: TLS handshake error from 168.63.129.16:55623: EOF
I0403 10:27:38.866170       1 log.go:172] http: TLS handshake error from 168.63.129.16:55712: EOF
I0403 10:27:48.866219       1 log.go:172] http: TLS handshake error from 168.63.129.16:55811: EOF
I0403 10:27:58.866360       1 log.go:172] http: TLS handshake error from 168.63.129.16:55897: EOF
...

Expected results:
2. Because we announce supporting Azure cloud, we should do this as better as possible, thus above errors in FRESH Azure env should not be seen for customer user experience. Though there is bug 1753443#c3 closed, it suggested others to do something to fix the issue. Here we suggest the cluster itself can do something to fix the issue :)

Additional info: