W0624 18:01:15.168104       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0624 18:01:15.170958       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 18:01:15.171354       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0624 18:01:15.171467       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0624 18:01:15.171546       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0624 18:01:15.171595       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0624 18:01:15.171627       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0624 18:01:15.176031       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 18:01:15.179332       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0624 18:01:16.178871       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 18:01:16.178936       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0624 18:01:16.183953       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 18:01:31.372829       1 log.go:245] http: TLS handshake error from 199.204.45.169:57634: EOF
I0624 18:04:16.203289       1 log.go:245] http: TLS handshake error from 199.204.45.169:53950: EOF
I0624 18:04:16.205385       1 log.go:245] http: TLS handshake error from 199.204.45.169:53962: EOF
I0624 18:04:16.217254       1 log.go:245] http: TLS handshake error from 199.204.45.169:53972: EOF
I0624 18:04:16.228968       1 log.go:245] http: TLS handshake error from 199.204.45.169:53986: EOF
I0624 18:15:38.864865       1 log.go:245] http: TLS handshake error from 199.204.45.169:60670: read tcp 10.0.0.199:10250->199.204.45.169:60670: read: connection reset by peer
I0624 18:15:39.282057       1 log.go:245] http: TLS handshake error from 199.204.45.169:60694: EOF
I0624 18:19:50.214046       1 log.go:245] http: TLS handshake error from 199.204.45.169:45706: EOF
I0624 18:23:11.466021       1 log.go:245] http: TLS handshake error from 199.204.45.169:43106: EOF
I0624 18:32:52.514665       1 log.go:245] http: TLS handshake error from 199.204.45.169:52294: EOF
I0624 18:41:52.547393       1 log.go:245] http: TLS handshake error from 199.204.45.169:43798: EOF
I0624 18:41:52.809339       1 log.go:245] http: TLS handshake error from 199.204.45.169:43830: EOF