W0628 19:50:23.672902       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0628 19:50:23.675241       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"
I0628 19:50:23.675620       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0628 19:50:23.675719       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0628 19:50:23.675791       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0628 19:50:23.675844       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0628 19:50:23.675874       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0628 19:50:23.681542       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"
I0628 19:50:23.685526       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0628 19:50:24.679555       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"]
I0628 19:50:24.679602       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0628 19:50:24.682583       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"]
I0628 19:50:36.204881       1 log.go:245] http: TLS handshake error from 199.204.45.216:58666: EOF
I0628 19:50:36.215853       1 log.go:245] http: TLS handshake error from 199.204.45.216:58676: read tcp 10.0.0.109:10250->199.204.45.216:58676: read: connection reset by peer
I0628 19:51:06.023396       1 log.go:245] http: TLS handshake error from 199.204.45.216:49542: read tcp 10.0.0.109:10250->199.204.45.216:49542: read: connection reset by peer
I0628 19:56:15.210112       1 log.go:245] http: TLS handshake error from 199.204.45.216:48012: EOF
I0628 19:56:15.211108       1 log.go:245] http: TLS handshake error from 199.204.45.216:48024: EOF
I0628 19:56:15.223470       1 log.go:245] http: TLS handshake error from 199.204.45.216:48032: EOF
I0628 19:56:15.279638       1 log.go:245] http: TLS handshake error from 199.204.45.216:48048: EOF
I0628 19:57:04.253010       1 log.go:245] http: TLS handshake error from 199.204.45.216:44490: EOF
I0628 19:57:04.256842       1 log.go:245] http: TLS handshake error from 199.204.45.216:44502: EOF
I0628 19:57:04.260496       1 log.go:245] http: TLS handshake error from 199.204.45.216:44512: EOF
I0628 19:57:04.848211       1 log.go:245] http: TLS handshake error from 199.204.45.216:37724: EOF
I0628 20:00:53.907353       1 log.go:245] http: TLS handshake error from 199.204.45.216:49754: EOF
I0628 20:00:54.103327       1 log.go:245] http: TLS handshake error from 199.204.45.216:49778: EOF
I0628 20:01:36.617757       1 log.go:245] http: TLS handshake error from 199.204.45.216:36936: EOF