W0624 17:55:37.913281       1 client_config.go:618] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0624 17:55:37.930509       1 webhook.go:128] "using dynamic certificate generating using CA stored in Secret resource" logger="cert-manager" secret_namespace="cert-manager" secret_name="cert-manager-webhook-ca"
I0624 17:55:37.930966       1 server.go:147] "listening for insecure healthz connections" logger="cert-manager.webhook" address=":6080"
I0624 17:55:37.931045       1 server.go:213] "listening for secure connections" logger="cert-manager.webhook" address=":10250"
I0624 17:55:37.936657       1 reflector.go:351] Caches populated for *v1.Secret from k8s.io/client-go@v0.29.7/tools/cache/reflector.go:229
I0624 17:55:38.936880       1 dynamic_source.go:255] "Updated cert-manager webhook TLS certificate" logger="cert-manager.webhook" DNSNames=["cert-manager-webhook","cert-manager-webhook.cert-manager","cert-manager-webhook.cert-manager.svc"]
I0624 17:55:49.836914       1 logs.go:59] http: TLS handshake error from 199.19.213.132:48010: EOF
I0624 17:55:49.945167       1 logs.go:59] http: TLS handshake error from 199.19.213.132:48020: EOF
I0624 17:56:19.274499       1 logs.go:59] http: TLS handshake error from 199.19.213.132:49312: EOF
I0624 17:56:19.276922       1 logs.go:59] http: TLS handshake error from 199.19.213.132:49320: EOF
I0624 17:56:19.571834       1 logs.go:59] http: TLS handshake error from 199.19.213.132:49344: EOF
I0624 18:00:42.992756       1 logs.go:59] http: TLS handshake error from 199.19.213.132:53202: read tcp 10.0.0.196:10250->199.19.213.132:53202: read: connection reset by peer
I0624 18:00:43.215139       1 logs.go:59] http: TLS handshake error from 199.19.213.132:53218: read tcp 10.0.0.196:10250->199.19.213.132:53218: read: connection reset by peer
I0624 18:00:43.220298       1 logs.go:59] http: TLS handshake error from 199.19.213.132:53232: EOF
I0624 18:00:43.238804       1 logs.go:59] http: TLS handshake error from 199.19.213.132:53248: EOF
I0624 18:01:53.122522       1 logs.go:59] http: TLS handshake error from 199.19.213.132:60208: EOF
I0624 18:01:53.124520       1 logs.go:59] http: TLS handshake error from 199.19.213.132:60212: EOF
I0624 18:01:53.221053       1 logs.go:59] http: TLS handshake error from 199.19.213.132:60214: EOF
I0624 18:02:42.050235       1 logs.go:59] http: TLS handshake error from 199.19.213.132:35598: EOF
I0624 18:02:42.054999       1 logs.go:59] http: TLS handshake error from 199.19.213.132:35604: EOF
I0624 18:02:42.141566       1 logs.go:59] http: TLS handshake error from 199.19.213.132:35636: EOF
I0624 18:02:42.354981       1 logs.go:59] http: TLS handshake error from 199.19.213.132:35642: EOF
I0624 18:02:42.359412       1 logs.go:59] http: TLS handshake error from 199.19.213.132:35654: EOF
I0624 18:07:04.349576       1 logs.go:59] http: TLS handshake error from 199.19.213.132:37742: EOF
I0624 18:07:05.010315       1 logs.go:59] http: TLS handshake error from 199.19.213.132:37748: EOF
I0624 18:07:05.012448       1 logs.go:59] http: TLS handshake error from 199.19.213.132:37752: read tcp 10.0.0.196:10250->199.19.213.132:37752: read: connection reset by peer