W0730 20:57:08.543911       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0730 20:57:08.546768       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"
I0730 20:57:08.547202       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0730 20:57:08.547340       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0730 20:57:08.547438       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0730 20:57:08.547507       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0730 20:57:08.547544       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0730 20:57:08.554323       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"
I0730 20:57:08.560644       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0730 20:57:09.554438       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"]
I0730 20:57:09.554511       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0730 20:57:09.558675       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"]
I0730 20:57:23.693186       1 log.go:245] http: TLS handshake error from 199.19.213.123:36864: EOF
I0730 21:08:21.396759       1 log.go:245] http: TLS handshake error from 199.19.213.123:35512: read tcp 10.0.0.139:10250->199.19.213.123:35512: read: connection reset by peer
I0730 21:12:09.183833       1 log.go:245] http: TLS handshake error from 199.19.213.123:44766: EOF
I0730 21:15:55.814789       1 log.go:245] http: TLS handshake error from 199.19.213.123:35698: EOF
I0730 21:19:34.764870       1 log.go:245] http: TLS handshake error from 199.19.213.123:52834: EOF
I0730 21:19:59.278425       1 log.go:245] http: TLS handshake error from 199.19.213.123:41394: EOF
I0730 21:19:59.919788       1 log.go:245] http: TLS handshake error from 199.19.213.123:41400: read tcp 10.0.0.139:10250->199.19.213.123:41400: read: connection reset by peer
I0730 21:26:23.584177       1 log.go:245] http: TLS handshake error from 199.19.213.123:60458: read tcp 10.0.0.139:10250->199.19.213.123:60458: read: connection reset by peer
I0730 21:26:23.782621       1 log.go:245] http: TLS handshake error from 199.19.213.123:60480: EOF
I0730 21:26:25.009614       1 log.go:245] http: TLS handshake error from 199.19.213.123:60496: read tcp 10.0.0.139:10250->199.19.213.123:60496: read: connection reset by peer
I0730 21:26:25.347545       1 log.go:245] http: TLS handshake error from 199.19.213.123:60500: EOF
I0730 21:29:29.099791       1 log.go:245] http: TLS handshake error from 199.19.213.123:46824: EOF
I0730 21:29:29.110564       1 log.go:245] http: TLS handshake error from 199.19.213.123:46830: read tcp 10.0.0.139:10250->199.19.213.123:46830: read: connection reset by peer
I0730 21:29:29.111166       1 log.go:245] http: TLS handshake error from 199.19.213.123:46842: EOF
I0730 21:33:32.233387       1 log.go:245] http: TLS handshake error from 199.19.213.123:42012: EOF
I0730 21:33:32.566476       1 log.go:245] http: TLS handshake error from 199.19.213.123:42038: read tcp 10.0.0.139:10250->199.19.213.123:42038: read: connection reset by peer