W0717 15:59:22.184307       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0717 15:59:22.187128       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"
I0717 15:59:22.188649       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0717 15:59:22.189452       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0717 15:59:22.189703       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0717 15:59:22.189802       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0717 15:59:22.189898       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0717 15:59:22.198863       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"
I0717 15:59:22.201755       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0717 15:59:23.194304       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"]
I0717 15:59:23.194357       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0717 15:59:23.197557       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"]
I0717 15:59:40.119098       1 log.go:245] http: TLS handshake error from 199.19.213.114:45804: EOF
I0717 15:59:40.227615       1 log.go:245] http: TLS handshake error from 199.19.213.114:45812: read tcp 10.0.0.215:10250->199.19.213.114:45812: read: connection reset by peer
I0717 16:00:08.131685       1 log.go:245] http: TLS handshake error from 199.19.213.114:39564: EOF
I0717 16:00:08.151190       1 log.go:245] http: TLS handshake error from 199.19.213.114:39568: EOF
I0717 16:05:46.637510       1 log.go:245] http: TLS handshake error from 199.19.213.114:34656: EOF
I0717 16:05:46.844661       1 log.go:245] http: TLS handshake error from 199.19.213.114:34666: EOF
I0717 16:07:41.415677       1 log.go:245] http: TLS handshake error from 199.19.213.114:55256: EOF
I0717 16:07:41.423154       1 log.go:245] http: TLS handshake error from 199.19.213.114:55266: EOF
I0717 16:07:41.423387       1 log.go:245] http: TLS handshake error from 199.19.213.114:55272: EOF
I0717 16:15:11.357215       1 log.go:245] http: TLS handshake error from 199.19.213.114:40032: EOF
I0717 16:15:11.373720       1 log.go:245] http: TLS handshake error from 199.19.213.114:40044: read tcp 10.0.0.215:10250->199.19.213.114:40044: read: connection reset by peer
I0717 16:24:26.737430       1 log.go:245] http: TLS handshake error from 199.19.213.114:53278: EOF
I0717 16:24:27.077069       1 log.go:245] http: TLS handshake error from 199.19.213.114:53308: EOF
I0717 16:26:03.311529       1 log.go:245] http: TLS handshake error from 199.19.213.114:40178: EOF
I0717 16:26:58.898708       1 log.go:245] http: TLS handshake error from 199.19.213.114:57668: EOF
I0717 16:26:58.996577       1 log.go:245] http: TLS handshake error from 199.19.213.114:57684: EOF
I0717 16:26:59.595029       1 log.go:245] http: TLS handshake error from 199.19.213.114:57698: EOF
I0717 16:26:59.696646       1 log.go:245] http: TLS handshake error from 199.19.213.114:57704: EOF
I0717 16:27:43.583344       1 log.go:245] http: TLS handshake error from 199.19.213.114:42706: EOF
I0717 16:30:17.684760       1 log.go:245] http: TLS handshake error from 199.19.213.114:60766: EOF
I0717 16:33:27.555667       1 log.go:245] http: TLS handshake error from 199.19.213.114:49342: EOF
I0717 16:33:27.805163       1 log.go:245] http: TLS handshake error from 199.19.213.114:49354: EOF
I0717 16:34:27.644778       1 log.go:245] http: TLS handshake error from 199.19.213.114:58804: EOF
I0717 16:34:27.654545       1 log.go:245] http: TLS handshake error from 199.19.213.114:58820: EOF
I0717 16:34:27.656915       1 log.go:245] http: TLS handshake error from 199.19.213.114:58832: EOF
I0717 16:34:27.658621       1 log.go:245] http: TLS handshake error from 199.19.213.114:58848: EOF
I0717 16:39:56.576096       1 log.go:245] http: TLS handshake error from 199.19.213.114:53872: EOF
I0717 16:39:56.591261       1 log.go:245] http: TLS handshake error from 199.19.213.114:53884: EOF
I0717 16:39:56.679679       1 log.go:245] http: TLS handshake error from 199.19.213.114:53916: EOF
I0717 16:39:57.229282       1 log.go:245] http: TLS handshake error from 199.19.213.114:53930: EOF
I0717 16:39:57.299890       1 log.go:245] http: TLS handshake error from 199.19.213.114:53938: EOF
I0717 16:39:57.909904       1 log.go:245] http: TLS handshake error from 199.19.213.114:53942: read tcp 10.0.0.215:10250->199.19.213.114:53942: read: connection reset by peer
I0717 16:42:23.177027       1 log.go:245] http: TLS handshake error from 199.19.213.114:42940: EOF
I0717 16:43:09.816698       1 log.go:245] http: TLS handshake error from 199.19.213.114:42382: EOF
I0717 16:43:09.927846       1 log.go:245] http: TLS handshake error from 199.19.213.114:42386: EOF
I0717 16:43:10.196497       1 log.go:245] http: TLS handshake error from 199.19.213.114:42394: EOF
I0717 16:46:49.231655       1 log.go:245] http: TLS handshake error from 199.19.213.114:53478: EOF
I0717 16:46:51.477144       1 log.go:245] http: TLS handshake error from 199.19.213.114:53482: EOF