W0724 21:33:49.571610       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0724 21:33:49.575212       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"
I0724 21:33:49.575805       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0724 21:33:49.575991       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0724 21:33:49.576261       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0724 21:33:49.576346       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0724 21:33:49.576488       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0724 21:33:49.582455       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"
I0724 21:33:49.586573       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0724 21:33:50.581845       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"]
I0724 21:33:50.581906       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0724 21:33:50.585675       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"]
I0724 21:34:26.268069       1 log.go:245] http: TLS handshake error from 199.204.45.44:51156: EOF
I0724 21:34:26.268799       1 log.go:245] http: TLS handshake error from 199.204.45.44:51166: EOF
I0724 21:34:26.282608       1 log.go:245] http: TLS handshake error from 199.204.45.44:51180: EOF
I0724 21:35:14.268497       1 log.go:245] http: TLS handshake error from 199.204.45.44:36524: EOF
I0724 21:42:23.369308       1 log.go:245] http: TLS handshake error from 199.204.45.44:47030: EOF
I0724 21:44:22.283905       1 log.go:245] http: TLS handshake error from 199.204.45.44:36720: EOF
I0724 21:44:22.318288       1 log.go:245] http: TLS handshake error from 199.204.45.44:36734: EOF
I0724 21:44:22.320569       1 log.go:245] http: TLS handshake error from 199.204.45.44:36756: EOF
I0724 21:44:22.321861       1 log.go:245] http: TLS handshake error from 199.204.45.44:36764: EOF
I0724 21:47:51.180337       1 log.go:245] http: TLS handshake error from 199.204.45.44:46448: EOF
I0724 21:48:39.671120       1 log.go:245] http: TLS handshake error from 199.204.45.44:58228: read tcp 10.0.0.28:10250->199.204.45.44:58228: read: connection reset by peer
I0724 21:50:31.657905       1 log.go:245] http: TLS handshake error from 199.204.45.44:37016: EOF
I0724 21:50:31.755387       1 log.go:245] http: TLS handshake error from 199.204.45.44:37028: EOF
I0724 21:50:32.695222       1 log.go:245] http: TLS handshake error from 199.204.45.44:37034: EOF
I0724 21:50:33.041704       1 log.go:245] http: TLS handshake error from 199.204.45.44:37048: EOF
I0724 21:55:21.572975       1 log.go:245] http: TLS handshake error from 199.204.45.44:33966: EOF
I0724 21:59:35.316840       1 log.go:245] http: TLS handshake error from 199.204.45.44:53052: EOF
I0724 21:59:35.523094       1 log.go:245] http: TLS handshake error from 199.204.45.44:53066: EOF
I0724 22:00:20.582876       1 log.go:245] http: TLS handshake error from 199.204.45.44:48302: EOF