W0812 00:36:54.927441       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0812 00:36:54.931260       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"
I0812 00:36:54.931770       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0812 00:36:54.931965       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0812 00:36:54.932093       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0812 00:36:54.932149       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0812 00:36:54.932219       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0812 00:36:54.936225       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"
I0812 00:36:54.941943       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0812 00:36:55.938864       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"]
I0812 00:36:55.938937       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0812 00:36:55.944561       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"]
I0812 00:37:36.515410       1 log.go:245] http: TLS handshake error from 199.19.213.23:56168: EOF
I0812 00:37:36.524629       1 log.go:245] http: TLS handshake error from 199.19.213.23:56170: EOF
I0812 00:38:02.699169       1 log.go:245] http: TLS handshake error from 199.19.213.23:34246: read tcp 10.0.0.71:10250->199.19.213.23:34246: read: connection reset by peer
I0812 00:43:23.449341       1 log.go:245] http: TLS handshake error from 199.19.213.23:42098: read tcp 10.0.0.71:10250->199.19.213.23:42098: read: connection reset by peer
I0812 00:43:23.450418       1 log.go:245] http: TLS handshake error from 199.19.213.23:42110: EOF
I0812 00:43:23.499287       1 log.go:245] http: TLS handshake error from 199.19.213.23:42118: read tcp 10.0.0.71:10250->199.19.213.23:42118: read: connection reset by peer
I0812 00:43:23.605703       1 log.go:245] http: TLS handshake error from 199.19.213.23:42120: EOF
I0812 00:43:23.758601       1 log.go:245] http: TLS handshake error from 199.19.213.23:42134: EOF
I0812 00:44:35.930377       1 log.go:245] http: TLS handshake error from 199.19.213.23:53278: read tcp 10.0.0.71:10250->199.19.213.23:53278: read: connection reset by peer
I0812 00:44:35.974934       1 log.go:245] http: TLS handshake error from 199.19.213.23:53322: EOF
I0812 00:48:52.690297       1 log.go:245] http: TLS handshake error from 199.19.213.23:57848: EOF