W0718 14:10:24.242623       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0718 14:10:24.244877       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"
I0718 14:10:24.246394       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0718 14:10:24.246553       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0718 14:10:24.246653       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0718 14:10:24.246732       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0718 14:10:24.246763       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0718 14:10:24.250936       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"
I0718 14:10:24.255397       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0718 14:10:25.250709       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"]
I0718 14:10:25.250748       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0718 14:10:25.253694       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"]
I0718 14:10:36.706259       1 log.go:245] http: TLS handshake error from 199.204.45.240:40900: EOF
I0718 14:10:36.706913       1 log.go:245] http: TLS handshake error from 199.204.45.240:40910: read tcp 10.0.0.96:10250->199.204.45.240:40910: read: connection reset by peer
I0718 14:10:36.719800       1 log.go:245] http: TLS handshake error from 199.204.45.240:40918: EOF
I0718 14:10:36.817052       1 log.go:245] http: TLS handshake error from 199.204.45.240:40934: EOF
I0718 14:11:02.776556       1 log.go:245] http: TLS handshake error from 199.204.45.240:49750: EOF
I0718 14:11:02.779815       1 log.go:245] http: TLS handshake error from 199.204.45.240:49762: EOF
I0718 14:15:27.021334       1 log.go:245] http: TLS handshake error from 199.204.45.240:56052: EOF
I0718 14:16:35.969870       1 log.go:245] http: TLS handshake error from 199.204.45.240:35168: EOF
I0718 14:16:35.971023       1 log.go:245] http: TLS handshake error from 199.204.45.240:35184: EOF
I0718 14:17:19.975913       1 log.go:245] http: TLS handshake error from 199.204.45.240:38106: EOF
I0718 14:17:19.977464       1 log.go:245] http: TLS handshake error from 199.204.45.240:38112: EOF
I0718 14:17:20.011804       1 log.go:245] http: TLS handshake error from 199.204.45.240:38128: EOF
I0718 14:17:20.013755       1 log.go:245] http: TLS handshake error from 199.204.45.240:38134: EOF
I0718 14:17:20.016176       1 log.go:245] http: TLS handshake error from 199.204.45.240:38136: EOF
I0718 14:22:03.445185       1 log.go:245] http: TLS handshake error from 199.204.45.240:42792: EOF