W0318 10:10:55.683287 1 client_config.go:618] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work. I0318 10:10:55.701354 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" I0318 10:10:55.701701 1 server.go:147] "listening for insecure healthz connections" logger="cert-manager.webhook" address=":6080" I0318 10:10:55.701766 1 server.go:213] "listening for secure connections" logger="cert-manager.webhook" address=":10250" I0318 10:10:55.704814 1 reflector.go:351] Caches populated for *v1.Secret from k8s.io/client-go@v0.29.7/tools/cache/reflector.go:229 I0318 10:10:56.707646 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"] I0318 10:11:10.856223 1 logs.go:59] http: TLS handshake error from 162.253.55.221:50374: EOF I0318 10:11:10.857062 1 logs.go:59] http: TLS handshake error from 162.253.55.221:50388: read tcp 10.0.0.213:10250->162.253.55.221:50388: read: connection reset by peer I0318 10:11:10.963454 1 logs.go:59] http: TLS handshake error from 162.253.55.221:50404: EOF I0318 10:11:10.964410 1 logs.go:59] http: TLS handshake error from 162.253.55.221:50408: EOF I0318 10:11:10.971062 1 logs.go:59] http: TLS handshake error from 162.253.55.221:50424: EOF I0318 10:13:16.750797 1 logs.go:59] http: TLS handshake error from 162.253.55.221:52136: EOF I0318 10:13:16.751849 1 logs.go:59] http: TLS handshake error from 162.253.55.221:52138: read tcp 10.0.0.213:10250->162.253.55.221:52138: read: connection reset by peer I0318 10:13:16.755078 1 logs.go:59] http: TLS handshake error from 162.253.55.221:52146: read tcp 10.0.0.213:10250->162.253.55.221:52146: read: connection reset by peer I0318 10:13:17.030242 1 logs.go:59] http: TLS handshake error from 162.253.55.221:52164: read tcp 10.0.0.213:10250->162.253.55.221:52164: read: connection reset by peer I0318 10:13:17.054595 1 logs.go:59] http: TLS handshake error from 162.253.55.221:52170: EOF I0318 10:13:17.057050 1 logs.go:59] http: TLS handshake error from 162.253.55.221:52186: EOF I0318 10:15:54.524088 1 logs.go:59] http: TLS handshake error from 162.253.55.221:47038: EOF I0318 10:17:47.161462 1 logs.go:59] http: TLS handshake error from 162.253.55.221:40410: EOF I0318 10:17:47.166640 1 logs.go:59] http: TLS handshake error from 162.253.55.221:40424: EOF I0318 10:17:47.181629 1 logs.go:59] http: TLS handshake error from 162.253.55.221:40428: EOF I0318 10:17:47.371744 1 logs.go:59] http: TLS handshake error from 162.253.55.221:40452: EOF I0318 10:17:47.396761 1 logs.go:59] http: TLS handshake error from 162.253.55.221:40466: read tcp 10.0.0.213:10250->162.253.55.221:40466: read: connection reset by peer I0318 10:17:55.272811 1 logs.go:59] http: TLS handshake error from 162.253.55.221:56314: read tcp 10.0.0.213:10250->162.253.55.221:56314: read: connection reset by peer I0318 10:18:15.110880 1 logs.go:59] http: TLS handshake error from 162.253.55.221:35846: read tcp 10.0.0.213:10250->162.253.55.221:35846: read: connection reset by peer I0318 10:21:35.654089 1 logs.go:59] http: TLS handshake error from 162.253.55.221:51610: EOF I0318 10:24:03.854787 1 logs.go:59] http: TLS handshake error from 162.253.55.221:37552: EOF I0318 10:24:04.231626 1 logs.go:59] http: TLS handshake error from 162.253.55.221:37580: EOF I0318 10:28:18.015013 1 logs.go:59] http: TLS handshake error from 162.253.55.221:36250: EOF