W0623 18:37:15.145481       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0623 18:37:15.147945       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"
I0623 18:37:15.148401       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0623 18:37:15.148508       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0623 18:37:15.148663       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0623 18:37:15.148728       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0623 18:37:15.148772       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
I0623 18:37:15.157535       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
E0623 18:37:15.157840       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"
I0623 18:37:16.152795       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"]
I0623 18:37:16.152845       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0623 18:37:16.158412       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"]
I0623 18:37:26.805234       1 log.go:245] http: TLS handshake error from 199.204.45.157:35422: EOF
I0623 18:37:26.821584       1 log.go:245] http: TLS handshake error from 199.204.45.157:35426: EOF
I0623 18:37:57.853560       1 log.go:245] http: TLS handshake error from 199.204.45.157:39566: EOF
I0623 18:37:57.876987       1 log.go:245] http: TLS handshake error from 199.204.45.157:39574: EOF
I0623 18:42:20.748207       1 log.go:245] http: TLS handshake error from 199.204.45.157:43600: EOF
I0623 18:43:25.538896       1 log.go:245] http: TLS handshake error from 199.204.45.157:38170: EOF
I0623 18:43:25.551538       1 log.go:245] http: TLS handshake error from 199.204.45.157:38178: EOF
I0623 18:43:25.649838       1 log.go:245] http: TLS handshake error from 199.204.45.157:38190: EOF
I0623 18:44:11.183520       1 log.go:245] http: TLS handshake error from 199.204.45.157:46030: EOF
I0623 18:44:11.258461       1 log.go:245] http: TLS handshake error from 199.204.45.157:46036: read tcp 10.0.0.57:10250->199.204.45.157:46036: read: connection reset by peer
I0623 18:48:02.771368       1 log.go:245] http: TLS handshake error from 199.204.45.157:60890: EOF
I0623 18:48:46.453097       1 log.go:245] http: TLS handshake error from 199.204.45.157:36986: EOF