W0417 18:44:36.094618       1 client_config.go:618] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0417 18:44:36.115216       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"
I0417 18:44:36.115605       1 server.go:147] "listening for insecure healthz connections" logger="cert-manager.webhook" address=":6080"
I0417 18:44:36.115711       1 server.go:213] "listening for secure connections" logger="cert-manager.webhook" address=":10250"
I0417 18:44:36.118738       1 reflector.go:351] Caches populated for *v1.Secret from k8s.io/client-go@v0.29.7/tools/cache/reflector.go:229
I0417 18:44:37.121679       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"]
I0417 18:44:47.671898       1 logs.go:59] http: TLS handshake error from 199.204.45.138:59952: EOF
I0417 18:44:47.768594       1 logs.go:59] http: TLS handshake error from 199.204.45.138:59968: EOF
I0417 18:45:12.103096       1 logs.go:59] http: TLS handshake error from 199.204.45.138:36858: EOF
I0417 18:45:12.107402       1 logs.go:59] http: TLS handshake error from 199.204.45.138:36884: EOF
I0417 18:45:12.509651       1 logs.go:59] http: TLS handshake error from 199.204.45.138:36886: EOF
I0417 18:49:48.562317       1 logs.go:59] http: TLS handshake error from 199.204.45.138:55400: EOF
I0417 18:49:48.800997       1 logs.go:59] http: TLS handshake error from 199.204.45.138:55412: EOF
I0417 18:50:55.770426       1 logs.go:59] http: TLS handshake error from 199.204.45.138:59698: EOF
I0417 18:50:55.771505       1 logs.go:59] http: TLS handshake error from 199.204.45.138:59704: EOF
I0417 18:50:55.781536       1 logs.go:59] http: TLS handshake error from 199.204.45.138:59716: EOF
I0417 18:50:55.819628       1 logs.go:59] http: TLS handshake error from 199.204.45.138:59732: EOF
I0417 18:50:55.867483       1 logs.go:59] http: TLS handshake error from 199.204.45.138:59742: EOF
I0417 18:51:40.162479       1 logs.go:59] http: TLS handshake error from 199.204.45.138:59438: EOF
I0417 18:51:40.164019       1 logs.go:59] http: TLS handshake error from 199.204.45.138:59454: EOF
I0417 18:51:40.167743       1 logs.go:59] http: TLS handshake error from 199.204.45.138:59456: EOF
I0417 18:51:40.187695       1 logs.go:59] http: TLS handshake error from 199.204.45.138:59470: EOF
I0417 18:55:26.938014       1 logs.go:59] http: TLS handshake error from 199.204.45.138:42366: EOF
I0417 18:57:51.792179       1 logs.go:59] http: TLS handshake error from 199.204.45.138:41114: EOF
I0417 18:57:52.092747       1 logs.go:59] http: TLS handshake error from 199.204.45.138:41118: EOF
I0417 18:58:49.700727       1 logs.go:59] http: TLS handshake error from 199.204.45.138:56452: read tcp 10.0.0.99:10250->199.204.45.138:56452: read: connection reset by peer
I0417 18:58:50.211790       1 logs.go:59] http: TLS handshake error from 199.204.45.138:56460: EOF
I0417 18:58:50.218348       1 logs.go:59] http: TLS handshake error from 199.204.45.138:56474: EOF
I0417 19:01:49.049696       1 logs.go:59] http: TLS handshake error from 199.204.45.138:57728: EOF
I0417 19:01:49.373933       1 logs.go:59] http: TLS handshake error from 199.204.45.138:57730: EOF
I0417 19:01:49.405361       1 logs.go:59] http: TLS handshake error from 199.204.45.138:57740: EOF