W0728 05:59:06.812785       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0728 05:59:06.817209       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"
I0728 05:59:06.821456       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0728 05:59:06.821704       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0728 05:59:06.821909       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0728 05:59:06.822030       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0728 05:59:06.822074       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0728 05:59:06.828425       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"
I0728 05:59:06.831754       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0728 05:59:07.830109       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"]
I0728 05:59:07.830181       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0728 05:59:07.833378       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"]
I0728 05:59:35.741600       1 log.go:245] http: TLS handshake error from 199.19.213.114:38560: EOF
I0728 05:59:35.757842       1 log.go:245] http: TLS handshake error from 199.19.213.114:38568: EOF
I0728 05:59:35.861227       1 log.go:245] http: TLS handshake error from 199.19.213.114:38590: EOF
I0728 06:02:32.552382       1 log.go:245] http: TLS handshake error from 199.19.213.114:58268: read tcp 10.0.0.50:10250->199.19.213.114:58268: read: connection reset by peer
I0728 06:02:32.565450       1 log.go:245] http: TLS handshake error from 199.19.213.114:58280: EOF
I0728 06:02:32.566495       1 log.go:245] http: TLS handshake error from 199.19.213.114:58294: EOF
I0728 06:02:32.777961       1 log.go:245] http: TLS handshake error from 199.19.213.114:58304: read tcp 10.0.0.50:10250->199.19.213.114:58304: read: connection reset by peer
I0728 06:12:06.052727       1 log.go:245] http: TLS handshake error from 199.19.213.114:49572: EOF
I0728 06:13:22.011478       1 log.go:245] http: TLS handshake error from 199.19.213.114:37160: EOF
I0728 06:13:22.024254       1 log.go:245] http: TLS handshake error from 199.19.213.114:37172: read tcp 10.0.0.50:10250->199.19.213.114:37172: read: connection reset by peer
I0728 06:18:28.954684       1 log.go:245] http: TLS handshake error from 199.19.213.114:54844: read tcp 10.0.0.50:10250->199.19.213.114:54844: read: connection reset by peer
I0728 06:26:58.366854       1 log.go:245] http: TLS handshake error from 199.19.213.114:50850: EOF
I0728 06:26:58.568758       1 log.go:245] http: TLS handshake error from 199.19.213.114:50856: EOF
I0728 06:44:52.764598       1 log.go:245] http: TLS handshake error from 199.19.213.114:41408: EOF
I0728 06:49:17.645940       1 log.go:245] http: TLS handshake error from 199.19.213.114:51676: EOF
I0728 06:49:18.088082       1 log.go:245] http: TLS handshake error from 199.19.213.114:51692: EOF