W0717 03:43:29.346334       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0717 03:43:29.350784       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"
I0717 03:43:29.351238       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0717 03:43:29.351379       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0717 03:43:29.351490       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0717 03:43:29.351575       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0717 03:43:29.351636       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0717 03:43:29.359821       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"
I0717 03:43:29.361442       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0717 03:43:30.357900       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"]
I0717 03:43:30.357966       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0717 03:43:30.362801       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"]
I0717 03:43:48.462317       1 log.go:245] http: TLS handshake error from 199.204.45.216:50512: read tcp 10.0.0.50:10250->199.204.45.216:50512: read: connection reset by peer
I0717 03:43:48.463095       1 log.go:245] http: TLS handshake error from 199.204.45.216:50518: read tcp 10.0.0.50:10250->199.204.45.216:50518: read: connection reset by peer
I0717 03:43:48.476064       1 log.go:245] http: TLS handshake error from 199.204.45.216:50530: EOF
I0717 03:43:48.477917       1 log.go:245] http: TLS handshake error from 199.204.45.216:50538: EOF
I0717 03:44:13.467657       1 log.go:245] http: TLS handshake error from 199.204.45.216:36150: EOF
I0717 03:46:08.512460       1 log.go:245] http: TLS handshake error from 199.204.45.216:46074: EOF
I0717 03:46:08.522058       1 log.go:245] http: TLS handshake error from 199.204.45.216:46080: read tcp 10.0.0.50:10250->199.204.45.216:46080: read: connection reset by peer
I0717 03:46:08.536892       1 log.go:245] http: TLS handshake error from 199.204.45.216:46092: EOF
I0717 03:46:13.571586       1 log.go:245] http: TLS handshake error from 199.204.45.216:50280: EOF
I0717 03:48:34.044664       1 log.go:245] http: TLS handshake error from 199.204.45.216:47746: EOF
I0717 03:49:42.712866       1 log.go:245] http: TLS handshake error from 199.204.45.216:59722: read tcp 10.0.0.50:10250->199.204.45.216:59722: read: connection reset by peer
I0717 03:49:42.724165       1 log.go:245] http: TLS handshake error from 199.204.45.216:59728: EOF
I0717 03:50:25.743861       1 log.go:245] http: TLS handshake error from 199.204.45.216:36940: read tcp 10.0.0.50:10250->199.204.45.216:36940: read: connection reset by peer
I0717 03:50:25.763404       1 log.go:245] http: TLS handshake error from 199.204.45.216:36962: EOF
I0717 03:50:25.763529       1 log.go:245] http: TLS handshake error from 199.204.45.216:36950: EOF
I0717 03:54:19.918475       1 log.go:245] http: TLS handshake error from 199.204.45.216:35184: read tcp 10.0.0.50:10250->199.204.45.216:35184: read: connection reset by peer
I0717 03:54:20.084948       1 log.go:245] http: TLS handshake error from 199.204.45.216:35194: EOF
I0717 03:57:48.877077       1 log.go:245] http: TLS handshake error from 199.204.45.216:58278: EOF
I0717 04:00:50.415194       1 log.go:245] http: TLS handshake error from 199.204.45.216:48160: EOF
I0717 04:07:05.801680       1 log.go:245] http: TLS handshake error from 199.204.45.216:51444: EOF
I0717 04:07:05.991655       1 log.go:245] http: TLS handshake error from 199.204.45.216:51474: EOF
I0717 04:08:41.533544       1 log.go:245] http: TLS handshake error from 199.204.45.216:34706: EOF
I0717 04:09:37.707924       1 log.go:245] http: TLS handshake error from 199.204.45.216:57044: EOF
I0717 04:09:37.824749       1 log.go:245] http: TLS handshake error from 199.204.45.216:57056: read tcp 10.0.0.50:10250->199.204.45.216:57056: read: connection reset by peer
I0717 04:13:01.676852       1 log.go:245] http: TLS handshake error from 199.204.45.216:54210: EOF
I0717 04:13:02.134820       1 log.go:245] http: TLS handshake error from 199.204.45.216:54234: EOF
I0717 04:13:03.697726       1 log.go:245] http: TLS handshake error from 199.204.45.216:54242: EOF
I0717 04:16:11.557911       1 log.go:245] http: TLS handshake error from 199.204.45.216:44794: EOF
I0717 04:17:05.488328       1 log.go:245] http: TLS handshake error from 199.204.45.216:45946: EOF
I0717 04:17:05.501492       1 log.go:245] http: TLS handshake error from 199.204.45.216:45962: EOF
I0717 04:22:39.982206       1 log.go:245] http: TLS handshake error from 199.204.45.216:46034: EOF
I0717 04:22:40.024211       1 log.go:245] http: TLS handshake error from 199.204.45.216:46044: EOF
I0717 04:25:06.541487       1 log.go:245] http: TLS handshake error from 199.204.45.216:39764: EOF
I0717 04:25:53.127036       1 log.go:245] http: TLS handshake error from 199.204.45.216:38438: EOF
I0717 04:34:26.121429       1 log.go:245] http: TLS handshake error from 199.204.45.216:59520: EOF