W0326 17:56:32.614882 1 client_config.go:618] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work. I0326 17:56:32.635412 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" I0326 17:56:32.635757 1 server.go:147] "listening for insecure healthz connections" logger="cert-manager.webhook" address=":6080" I0326 17:56:32.635887 1 server.go:213] "listening for secure connections" logger="cert-manager.webhook" address=":10250" I0326 17:56:32.639346 1 reflector.go:351] Caches populated for *v1.Secret from k8s.io/client-go@v0.29.7/tools/cache/reflector.go:229 I0326 17:56:33.642546 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"] I0326 17:59:02.795923 1 logs.go:59] http: TLS handshake error from 199.19.213.169:33702: EOF I0326 17:59:02.796697 1 logs.go:59] http: TLS handshake error from 199.19.213.169:33706: EOF I0326 17:59:02.800734 1 logs.go:59] http: TLS handshake error from 199.19.213.169:33712: EOF I0326 17:59:02.808455 1 logs.go:59] http: TLS handshake error from 199.19.213.169:33720: EOF I0326 17:59:02.814086 1 logs.go:59] http: TLS handshake error from 199.19.213.169:33736: EOF I0326 17:59:02.824371 1 logs.go:59] http: TLS handshake error from 199.19.213.169:33738: read tcp 10.0.0.39:10250->199.19.213.169:33738: read: connection reset by peer I0326 17:59:03.431536 1 logs.go:59] http: TLS handshake error from 199.19.213.169:33742: read tcp 10.0.0.39:10250->199.19.213.169:33742: read: connection reset by peer I0326 18:01:34.633119 1 logs.go:59] http: TLS handshake error from 199.19.213.169:37632: EOF I0326 18:01:34.635405 1 logs.go:59] http: TLS handshake error from 199.19.213.169:37648: read tcp 10.0.0.39:10250->199.19.213.169:37648: read: connection reset by peer I0326 18:01:34.845453 1 logs.go:59] http: TLS handshake error from 199.19.213.169:37662: EOF I0326 18:02:43.865082 1 logs.go:59] http: TLS handshake error from 199.19.213.169:33300: EOF I0326 18:02:43.866324 1 logs.go:59] http: TLS handshake error from 199.19.213.169:33312: EOF I0326 18:02:43.876434 1 logs.go:59] http: TLS handshake error from 199.19.213.169:33314: read tcp 10.0.0.39:10250->199.19.213.169:33314: read: connection reset by peer I0326 18:02:43.907586 1 logs.go:59] http: TLS handshake error from 199.19.213.169:33316: EOF I0326 18:03:28.079139 1 logs.go:59] http: TLS handshake error from 199.19.213.169:58970: EOF I0326 18:03:28.095172 1 logs.go:59] http: TLS handshake error from 199.19.213.169:58996: EOF I0326 18:03:28.110465 1 logs.go:59] http: TLS handshake error from 199.19.213.169:59020: EOF I0326 18:07:18.316066 1 logs.go:59] http: TLS handshake error from 199.19.213.169:47820: EOF I0326 18:09:41.540290 1 logs.go:59] http: TLS handshake error from 199.19.213.169:35946: EOF I0326 18:09:41.858066 1 logs.go:59] http: TLS handshake error from 199.19.213.169:35950: EOF I0326 18:09:41.863429 1 logs.go:59] http: TLS handshake error from 199.19.213.169:35962: EOF I0326 18:10:50.721382 1 logs.go:59] http: TLS handshake error from 199.19.213.169:43792: EOF I0326 18:10:51.044336 1 logs.go:59] http: TLS handshake error from 199.19.213.169:53272: EOF I0326 18:14:00.086197 1 logs.go:59] http: TLS handshake error from 199.19.213.169:49764: EOF I0326 18:14:00.090199 1 logs.go:59] http: TLS handshake error from 199.19.213.169:49770: EOF