W0416 16:42:55.658952       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0416 16:42:55.661677       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"
I0416 16:42:55.662075       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0416 16:42:55.662176       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0416 16:42:55.662287       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0416 16:42:55.662330       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0416 16:42:55.662364       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0416 16:42:55.668381       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"
I0416 16:42:55.672310       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0416 16:42:56.667409       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"]
I0416 16:42:56.667479       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0416 16:42:56.671682       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"]
I0416 16:43:23.059560       1 log.go:245] http: TLS handshake error from 199.204.45.169:48250: EOF
I0416 16:43:23.184103       1 log.go:245] http: TLS handshake error from 199.204.45.169:48262: EOF
I0416 16:48:32.801948       1 log.go:245] http: TLS handshake error from 199.204.45.169:51342: EOF
I0416 16:48:33.175512       1 log.go:245] http: TLS handshake error from 199.204.45.169:51348: EOF
I0416 16:48:34.485986       1 log.go:245] http: TLS handshake error from 199.204.45.169:51350: EOF
I0416 16:48:34.729722       1 log.go:245] http: TLS handshake error from 199.204.45.169:51364: EOF
I0416 16:49:30.854722       1 log.go:245] http: TLS handshake error from 199.204.45.169:39822: EOF
I0416 16:49:30.865317       1 log.go:245] http: TLS handshake error from 199.204.45.169:39838: EOF
I0416 16:49:30.865601       1 log.go:245] http: TLS handshake error from 199.204.45.169:39844: EOF
I0416 16:49:30.966991       1 log.go:245] http: TLS handshake error from 199.204.45.169:39854: EOF
I0416 16:50:25.902983       1 log.go:245] http: TLS handshake error from 199.204.45.169:35076: EOF
I0416 16:54:19.637757       1 log.go:245] http: TLS handshake error from 199.204.45.169:51154: EOF
I0416 16:54:19.966720       1 log.go:245] http: TLS handshake error from 199.204.45.169:51178: EOF