W0624 17:55:48.164120       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0624 17:55:48.166536       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"
I0624 17:55:48.167172       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0624 17:55:48.167296       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0624 17:55:48.167375       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0624 17:55:48.167430       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0624 17:55:48.167466       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0624 17:55:48.172851       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"
I0624 17:55:48.176109       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0624 17:55:49.171919       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"]
I0624 17:55:49.171962       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0624 17:55:49.174932       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"]
I0624 17:55:59.708808       1 log.go:245] http: TLS handshake error from 199.19.213.130:55722: EOF
I0624 17:55:59.710838       1 log.go:245] http: TLS handshake error from 199.19.213.130:55734: EOF
I0624 17:55:59.809144       1 log.go:245] http: TLS handshake error from 199.19.213.130:55744: EOF
I0624 17:56:27.975476       1 log.go:245] http: TLS handshake error from 199.19.213.130:32814: EOF
I0624 18:00:44.170841       1 log.go:245] http: TLS handshake error from 199.19.213.130:34804: EOF
I0624 18:00:44.532089       1 log.go:245] http: TLS handshake error from 199.19.213.130:34826: read tcp 10.0.0.58:10250->199.19.213.130:34826: read: connection reset by peer
I0624 18:01:51.196762       1 log.go:245] http: TLS handshake error from 199.19.213.130:45548: EOF
I0624 18:01:51.216562       1 log.go:245] http: TLS handshake error from 199.19.213.130:45564: EOF
I0624 18:02:37.588655       1 log.go:245] http: TLS handshake error from 199.19.213.130:46050: EOF
I0624 18:02:37.620281       1 log.go:245] http: TLS handshake error from 199.19.213.130:46054: EOF
I0624 18:06:31.415879       1 log.go:245] http: TLS handshake error from 199.19.213.130:54024: EOF
I0624 18:06:31.698854       1 log.go:245] http: TLS handshake error from 199.19.213.130:54048: read tcp 10.0.0.58:10250->199.19.213.130:54048: read: connection reset by peer