W0624 05:28:57.932692       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0624 05:28:57.935151       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 05:28:57.935541       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0624 05:28:57.935870       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0624 05:28:57.935946       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0624 05:28:57.935999       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0624 05:28:57.936033       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0624 05:28:57.943766       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 05:28:57.945218       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0624 05:28:58.941801       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 05:28:58.941863       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0624 05:28:58.946591       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 05:29:09.348606       1 log.go:245] http: TLS handshake error from 199.204.45.4:51984: EOF
I0624 05:29:09.459697       1 log.go:245] http: TLS handshake error from 199.204.45.4:52010: read tcp 10.0.0.4:10250->199.204.45.4:52010: read: connection reset by peer
I0624 05:29:34.456060       1 log.go:245] http: TLS handshake error from 199.204.45.4:55724: EOF
I0624 05:29:34.958466       1 log.go:245] http: TLS handshake error from 199.204.45.4:55734: EOF
I0624 05:31:07.635290       1 log.go:245] http: TLS handshake error from 199.204.45.4:53358: EOF
I0624 05:39:35.598713       1 log.go:245] http: TLS handshake error from 199.204.45.4:39020: EOF
I0624 05:46:29.140238       1 log.go:245] http: TLS handshake error from 199.204.45.4:43852: read tcp 10.0.0.4:10250->199.204.45.4:43852: read: connection reset by peer
I0624 05:46:29.159739       1 log.go:245] http: TLS handshake error from 199.204.45.4:43860: EOF
I0624 05:54:29.437273       1 log.go:245] http: TLS handshake error from 199.204.45.4:46038: read tcp 10.0.0.4:10250->199.204.45.4:46038: read: connection reset by peer
I0624 05:56:10.570199       1 log.go:245] http: TLS handshake error from 199.204.45.4:36972: EOF
I0624 05:56:10.806161       1 log.go:245] http: TLS handshake error from 199.204.45.4:36988: read tcp 10.0.0.4:10250->199.204.45.4:36988: read: connection reset by peer
I0624 06:00:42.100941       1 log.go:245] http: TLS handshake error from 199.204.45.4:37992: EOF
I0624 06:04:01.338960       1 log.go:245] http: TLS handshake error from 199.204.45.4:37330: EOF
I0624 06:04:01.779130       1 log.go:245] http: TLS handshake error from 199.204.45.4:37342: EOF
I0624 06:04:50.165574       1 log.go:245] http: TLS handshake error from 199.204.45.4:42250: EOF