W0619 22:53:08.878048       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0619 22:53:08.882775       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"
I0619 22:53:08.883139       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0619 22:53:08.883229       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0619 22:53:08.883295       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0619 22:53:08.883323       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0619 22:53:08.883354       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
I0619 22:53:08.890452       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
E0619 22:53:08.890572       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"
I0619 22:53:09.888146       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"]
I0619 22:53:09.888230       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0619 22:53:09.893660       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"]
I0619 22:53:51.759233       1 log.go:245] http: TLS handshake error from 199.204.45.248:41660: read tcp 10.0.0.239:10250->199.204.45.248:41660: read: connection reset by peer
I0619 22:57:59.981069       1 log.go:245] http: TLS handshake error from 199.204.45.248:56254: EOF
I0619 22:59:06.039978       1 log.go:245] http: TLS handshake error from 199.204.45.248:59482: read tcp 10.0.0.239:10250->199.204.45.248:59482: read: connection reset by peer
I0619 22:59:06.040868       1 log.go:245] http: TLS handshake error from 199.204.45.248:59488: EOF
I0619 22:59:06.055026       1 log.go:245] http: TLS handshake error from 199.204.45.248:59498: EOF
I0619 22:59:54.501715       1 log.go:245] http: TLS handshake error from 199.204.45.248:40144: EOF
I0619 22:59:54.527429       1 log.go:245] http: TLS handshake error from 199.204.45.248:40184: read tcp 10.0.0.239:10250->199.204.45.248:40184: read: connection reset by peer
I0619 22:59:54.530745       1 log.go:245] http: TLS handshake error from 199.204.45.248:40192: EOF
I0619 22:59:55.015003       1 log.go:245] http: TLS handshake error from 199.204.45.248:40204: EOF
I0619 22:59:55.015130       1 log.go:245] http: TLS handshake error from 199.204.45.248:40200: EOF
I0619 23:03:43.283974       1 log.go:245] http: TLS handshake error from 199.204.45.248:53986: EOF
I0619 23:03:43.608745       1 log.go:245] http: TLS handshake error from 199.204.45.248:54006: read tcp 10.0.0.239:10250->199.204.45.248:54006: read: connection reset by peer
I0619 23:04:27.945803       1 log.go:245] http: TLS handshake error from 199.204.45.248:47934: EOF