W0525 00:38:26.909702 1 client_config.go:618] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work. I0525 00:38:26.928811 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" I0525 00:38:26.929100 1 server.go:147] "listening for insecure healthz connections" logger="cert-manager.webhook" address=":6080" I0525 00:38:26.929162 1 server.go:213] "listening for secure connections" logger="cert-manager.webhook" address=":10250" I0525 00:38:26.931767 1 reflector.go:351] Caches populated for *v1.Secret from k8s.io/client-go@v0.29.7/tools/cache/reflector.go:229 I0525 00:38:27.935255 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"] I0525 00:38:39.418070 1 logs.go:59] http: TLS handshake error from 199.204.45.138:55734: EOF I0525 00:38:39.419664 1 logs.go:59] http: TLS handshake error from 199.204.45.138:55744: EOF I0525 00:38:39.465359 1 logs.go:59] http: TLS handshake error from 199.204.45.138:55748: EOF I0525 00:38:39.521513 1 logs.go:59] http: TLS handshake error from 199.204.45.138:55758: EOF I0525 00:38:39.539219 1 logs.go:59] http: TLS handshake error from 199.204.45.138:55764: EOF I0525 00:38:39.540278 1 logs.go:59] http: TLS handshake error from 199.204.45.138:55768: read tcp 10.0.0.168:10250->199.204.45.138:55768: read: connection reset by peer I0525 00:38:39.548218 1 logs.go:59] http: TLS handshake error from 199.204.45.138:55774: read tcp 10.0.0.168:10250->199.204.45.138:55774: read: connection reset by peer I0525 00:39:05.001533 1 logs.go:59] http: TLS handshake error from 199.204.45.138:59126: EOF I0525 00:39:05.003541 1 logs.go:59] http: TLS handshake error from 199.204.45.138:59128: EOF I0525 00:39:05.004849 1 logs.go:59] http: TLS handshake error from 199.204.45.138:59130: read tcp 10.0.0.168:10250->199.204.45.138:59130: read: connection reset by peer I0525 00:39:05.035162 1 logs.go:59] http: TLS handshake error from 199.204.45.138:59138: EOF I0525 00:39:05.414133 1 logs.go:59] http: TLS handshake error from 199.204.45.138:59142: read tcp 10.0.0.168:10250->199.204.45.138:59142: read: connection reset by peer I0525 00:43:19.745485 1 logs.go:59] http: TLS handshake error from 199.204.45.138:58764: EOF I0525 00:45:07.582067 1 logs.go:59] http: TLS handshake error from 199.204.45.138:59218: EOF I0525 00:45:07.582412 1 logs.go:59] http: TLS handshake error from 199.204.45.138:59204: EOF I0525 00:45:07.608725 1 logs.go:59] http: TLS handshake error from 199.204.45.138:59222: EOF I0525 00:45:07.612949 1 logs.go:59] http: TLS handshake error from 199.204.45.138:59240: EOF I0525 00:45:07.633653 1 logs.go:59] http: TLS handshake error from 199.204.45.138:59284: EOF I0525 00:45:07.635084 1 logs.go:59] http: TLS handshake error from 199.204.45.138:59270: EOF I0525 00:48:39.302212 1 logs.go:59] http: TLS handshake error from 199.204.45.138:46872: EOF I0525 00:48:39.733317 1 logs.go:59] http: TLS handshake error from 199.204.45.138:46880: EOF I0525 00:48:39.764625 1 logs.go:59] http: TLS handshake error from 199.204.45.138:46886: EOF I0525 00:48:39.769344 1 logs.go:59] http: TLS handshake error from 199.204.45.138:46896: EOF