W0716 15:48:39.770426       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0716 15:48:39.776789       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"
I0716 15:48:39.777464       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0716 15:48:39.777652       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0716 15:48:39.777805       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0716 15:48:39.777892       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0716 15:48:39.777965       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0716 15:48:39.784492       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"
I0716 15:48:39.785910       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0716 15:48:40.785876       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"]
I0716 15:48:40.786020       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0716 15:48:40.790718       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"]
I0716 15:48:51.200439       1 log.go:245] http: TLS handshake error from 199.204.45.109:38064: EOF
I0716 15:53:32.975733       1 log.go:245] http: TLS handshake error from 199.204.45.109:41958: EOF
I0716 15:53:33.147646       1 log.go:245] http: TLS handshake error from 199.204.45.109:41980: EOF
I0716 15:53:33.166247       1 log.go:245] http: TLS handshake error from 199.204.45.109:41986: read tcp 10.0.0.240:10250->199.204.45.109:41986: read: connection reset by peer
I0716 15:54:38.294577       1 log.go:245] http: TLS handshake error from 199.204.45.109:39402: EOF
I0716 15:55:29.062838       1 log.go:245] http: TLS handshake error from 199.204.45.109:47556: EOF
I0716 15:55:29.063535       1 log.go:245] http: TLS handshake error from 199.204.45.109:47570: EOF
I0716 15:55:29.100834       1 log.go:245] http: TLS handshake error from 199.204.45.109:47584: EOF
I0716 15:55:29.102107       1 log.go:245] http: TLS handshake error from 199.204.45.109:47606: EOF
I0716 15:59:19.835138       1 log.go:245] http: TLS handshake error from 199.204.45.109:33856: read tcp 10.0.0.240:10250->199.204.45.109:33856: read: connection reset by peer
I0716 16:00:02.880129       1 log.go:245] http: TLS handshake error from 199.204.45.109:36460: EOF
I0716 16:00:03.153506       1 log.go:245] http: TLS handshake error from 199.204.45.109:36462: EOF