W0730 20:59:59.996337       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0730 20:59:59.998784       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"
I0730 20:59:59.999217       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0730 20:59:59.999372       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0730 20:59:59.999470       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0730 20:59:59.999534       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0730 20:59:59.999587       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0730 21:00:00.009524       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"
I0730 21:00:00.012984       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0730 21:00:01.005201       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"]
I0730 21:00:01.005246       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0730 21:00:01.008294       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"]
I0730 21:00:14.913927       1 log.go:245] http: TLS handshake error from 199.204.45.22:55098: EOF
I0730 21:00:15.197147       1 log.go:245] http: TLS handshake error from 199.204.45.22:55114: EOF
I0730 21:00:41.789869       1 log.go:245] http: TLS handshake error from 199.204.45.22:34060: EOF
I0730 21:00:41.792608       1 log.go:245] http: TLS handshake error from 199.204.45.22:34076: EOF
I0730 21:00:42.302566       1 log.go:245] http: TLS handshake error from 199.204.45.22:34090: EOF
I0730 21:04:58.311413       1 log.go:245] http: TLS handshake error from 199.204.45.22:59432: EOF
I0730 21:04:58.526306       1 log.go:245] http: TLS handshake error from 199.204.45.22:59448: EOF
I0730 21:06:03.613752       1 log.go:245] http: TLS handshake error from 199.204.45.22:53370: read tcp 10.0.0.106:10250->199.204.45.22:53370: read: connection reset by peer
I0730 21:06:03.614006       1 log.go:245] http: TLS handshake error from 199.204.45.22:53378: EOF
I0730 21:06:03.627789       1 log.go:245] http: TLS handshake error from 199.204.45.22:53380: EOF
I0730 21:06:53.242782       1 log.go:245] http: TLS handshake error from 199.204.45.22:53482: read tcp 10.0.0.106:10250->199.204.45.22:53482: read: connection reset by peer
I0730 21:10:30.271351       1 log.go:245] http: TLS handshake error from 199.204.45.22:53334: EOF
I0730 21:10:30.497762       1 log.go:245] http: TLS handshake error from 199.204.45.22:53356: read tcp 10.0.0.106:10250->199.204.45.22:53356: read: connection reset by peer
I0730 21:11:14.592305       1 log.go:245] http: TLS handshake error from 199.204.45.22:59048: EOF
I0730 21:11:14.947888       1 log.go:245] http: TLS handshake error from 199.204.45.22:59058: EOF