W0619 13:34:09.701654       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0619 13:34:09.703416       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 13:34:09.703874       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0619 13:34:09.704036       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0619 13:34:09.704178       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0619 13:34:09.704229       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0619 13:34:09.704324       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
I0619 13:34:09.710923       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
E0619 13:34:09.711056       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 13:34:10.708814       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 13:34:10.708921       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0619 13:34:10.712186       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 13:34:24.453824       1 log.go:245] http: TLS handshake error from 199.19.213.40:41168: EOF
I0619 13:41:33.107860       1 log.go:245] http: TLS handshake error from 199.19.213.40:45334: EOF
I0619 13:41:33.108839       1 log.go:245] http: TLS handshake error from 199.19.213.40:45344: EOF
I0619 13:41:33.185740       1 log.go:245] http: TLS handshake error from 199.19.213.40:45360: EOF
I0619 13:42:19.448163       1 log.go:245] http: TLS handshake error from 199.19.213.40:49478: EOF
I0619 13:42:19.450841       1 log.go:245] http: TLS handshake error from 199.19.213.40:49462: EOF
I0619 13:42:19.478869       1 log.go:245] http: TLS handshake error from 199.19.213.40:49480: EOF
I0619 13:42:19.484119       1 log.go:245] http: TLS handshake error from 199.19.213.40:49488: read tcp 10.0.0.195:10250->199.19.213.40:49488: read: connection reset by peer
I0619 13:42:19.493378       1 log.go:245] http: TLS handshake error from 199.19.213.40:49504: EOF
I0619 13:42:19.509420       1 log.go:245] http: TLS handshake error from 199.19.213.40:49512: read tcp 10.0.0.195:10250->199.19.213.40:49512: read: connection reset by peer
I0619 13:42:28.069872       1 log.go:245] http: TLS handshake error from 199.19.213.40:49526: EOF