W0702 19:46:31.985193 1 client_config.go:659] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work. I0702 19:46:31.988836 1 webhook.go:128] "using dynamic certificate generating using CA stored in Secret resource" logger="cert-manager.webhook.webhook" secret_namespace="cert-manager" secret_name="cert-manager-webhook-ca" I0702 19:46:31.989224 1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080 I0702 19:46:31.989318 1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate" I0702 19:46:31.989417 1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate" I0702 19:46:31.989459 1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook" I0702 19:46:31.989493 1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250 E0702 19:46:31.997605 1 dynamic_source.go:221] "Failed to generate serving certificate, retrying..." err="failed verifying CA keypair: tls: failed to find any PEM data in certificate input" logger="cert-manager" interval="1s" I0702 19:46:32.005883 1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232 I0702 19:46:32.996803 1 dynamic_source.go:290] "Updated cert-manager TLS certificate" logger="cert-manager" DNSNames=["cert-manager-webhook","cert-manager-webhook.cert-manager","cert-manager-webhook.cert-manager.svc"] I0702 19:46:32.996867 1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager" I0702 19:46:33.000124 1 dynamic_source.go:290] "Updated cert-manager TLS certificate" logger="cert-manager" DNSNames=["cert-manager-webhook","cert-manager-webhook.cert-manager","cert-manager-webhook.cert-manager.svc"] I0702 19:46:52.021613 1 log.go:245] http: TLS handshake error from 199.204.45.3:37192: EOF I0702 19:50:39.969529 1 log.go:245] http: TLS handshake error from 199.204.45.3:33052: EOF I0702 19:50:39.971561 1 log.go:245] http: TLS handshake error from 199.204.45.3:33064: EOF I0702 19:50:39.981480 1 log.go:245] http: TLS handshake error from 199.204.45.3:33068: read tcp 10.0.0.147:10250->199.204.45.3:33068: read: connection reset by peer I0702 19:50:39.983039 1 log.go:245] http: TLS handshake error from 199.204.45.3:33080: EOF I0702 19:53:32.264991 1 log.go:245] http: TLS handshake error from 199.204.45.3:37542: read tcp 10.0.0.147:10250->199.204.45.3:37542: read: connection reset by peer I0702 19:55:33.423045 1 log.go:245] http: TLS handshake error from 199.204.45.3:54092: EOF I0702 19:55:33.450996 1 log.go:245] http: TLS handshake error from 199.204.45.3:54106: EOF I0702 19:55:33.454901 1 log.go:245] http: TLS handshake error from 199.204.45.3:54128: EOF I0702 19:59:59.402538 1 log.go:245] http: TLS handshake error from 199.204.45.3:47934: EOF I0702 19:59:59.773724 1 log.go:245] http: TLS handshake error from 199.204.45.3:47954: read tcp 10.0.0.147:10250->199.204.45.3:47954: read: connection reset by peer I0702 20:03:01.192564 1 log.go:245] http: TLS handshake error from 199.204.45.3:59932: EOF I0702 20:17:43.242255 1 log.go:245] http: TLS handshake error from 199.204.45.3:58706: read tcp 10.0.0.147:10250->199.204.45.3:58706: read: connection reset by peer I0702 20:18:50.433182 1 log.go:245] http: TLS handshake error from 199.204.45.3:42334: EOF I0702 20:22:53.128887 1 log.go:245] http: TLS handshake error from 199.204.45.3:36854: EOF I0702 20:22:53.690024 1 log.go:245] http: TLS handshake error from 199.204.45.3:36874: EOF I0702 20:22:55.333513 1 log.go:245] http: TLS handshake error from 199.204.45.3:33174: EOF I0702 20:26:40.930327 1 log.go:245] http: TLS handshake error from 199.204.45.3:40364: read tcp 10.0.0.147:10250->199.204.45.3:40364: read: connection reset by peer