W0619 00:18:27.107931       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0619 00:18:27.111875       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"
I0619 00:18:27.112534       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0619 00:18:27.112699       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0619 00:18:27.112849       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0619 00:18:27.112944       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0619 00:18:27.113002       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0619 00:18:27.119640       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"
I0619 00:18:27.125497       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0619 00:18:28.118809       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"]
I0619 00:18:28.118880       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0619 00:18:28.122832       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"]
I0619 00:18:40.677049       1 log.go:245] http: TLS handshake error from 199.204.45.70:39856: EOF
I0619 00:18:40.678054       1 log.go:245] http: TLS handshake error from 199.204.45.70:39864: EOF
I0619 00:21:40.091594       1 log.go:245] http: TLS handshake error from 199.204.45.70:56930: EOF
I0619 00:21:40.434161       1 log.go:245] http: TLS handshake error from 199.204.45.70:56952: EOF
I0619 00:25:25.852069       1 log.go:245] http: TLS handshake error from 199.204.45.70:42922: EOF
I0619 00:26:09.449852       1 log.go:245] http: TLS handshake error from 199.204.45.70:44706: EOF
I0619 00:26:09.482023       1 log.go:245] http: TLS handshake error from 199.204.45.70:44722: EOF
I0619 00:32:39.265955       1 log.go:245] http: TLS handshake error from 199.204.45.70:49358: EOF
I0619 00:32:39.548130       1 log.go:245] http: TLS handshake error from 199.204.45.70:49374: EOF
I0619 00:33:48.767285       1 log.go:245] http: TLS handshake error from 199.204.45.70:57618: EOF
I0619 00:46:08.854439       1 log.go:245] http: TLS handshake error from 199.204.45.70:52082: EOF
I0619 00:53:08.036587       1 log.go:245] http: TLS handshake error from 199.204.45.70:51582: read tcp 10.0.0.62:10250->199.204.45.70:51582: read: connection reset by peer
I0619 00:56:34.457305       1 log.go:245] http: TLS handshake error from 199.204.45.70:57896: EOF
I0619 00:56:35.683709       1 log.go:245] http: TLS handshake error from 199.204.45.70:57918: EOF
I0619 00:56:54.067059       1 log.go:245] http: TLS handshake error from 199.204.45.70:45390: read tcp 10.0.0.62:10250->199.204.45.70:45390: read: connection reset by peer
I0619 00:56:54.081845       1 log.go:245] http: TLS handshake error from 199.204.45.70:45394: EOF
I0619 00:56:54.090211       1 log.go:245] http: TLS handshake error from 199.204.45.70:45406: EOF