W0903 16:17:52.042092       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0903 16:17:52.045238       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"
I0903 16:17:52.045718       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0903 16:17:52.045916       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0903 16:17:52.046100       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0903 16:17:52.046166       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0903 16:17:52.046201       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0903 16:17:52.052450       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"
I0903 16:17:52.055978       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0903 16:17:53.055314       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"]
I0903 16:17:53.055368       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0903 16:17:53.060259       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"]
I0903 16:18:06.032594       1 log.go:245] http: TLS handshake error from 162.253.55.55:39390: EOF
I0903 16:18:06.046951       1 log.go:245] http: TLS handshake error from 162.253.55.55:39400: EOF
I0903 16:18:06.157515       1 log.go:245] http: TLS handshake error from 162.253.55.55:39418: read tcp 10.0.0.1:10250->162.253.55.55:39418: read: connection reset by peer
I0903 16:18:35.282860       1 log.go:245] http: TLS handshake error from 162.253.55.55:44398: EOF
I0903 16:23:42.562105       1 log.go:245] http: TLS handshake error from 162.253.55.55:56074: EOF
I0903 16:24:50.370589       1 log.go:245] http: TLS handshake error from 162.253.55.55:49980: read tcp 10.0.0.1:10250->162.253.55.55:49980: read: connection reset by peer
I0903 16:24:50.371753       1 log.go:245] http: TLS handshake error from 162.253.55.55:49990: read tcp 10.0.0.1:10250->162.253.55.55:49990: read: connection reset by peer
I0903 16:24:50.392230       1 log.go:245] http: TLS handshake error from 162.253.55.55:50006: EOF
I0903 16:24:50.463243       1 log.go:245] http: TLS handshake error from 162.253.55.55:50022: EOF
I0903 16:25:35.962793       1 log.go:245] http: TLS handshake error from 162.253.55.55:47738: read tcp 10.0.0.1:10250->162.253.55.55:47738: read: connection reset by peer
I0903 16:25:35.964002       1 log.go:245] http: TLS handshake error from 162.253.55.55:47724: EOF
I0903 16:30:08.372939       1 log.go:245] http: TLS handshake error from 162.253.55.55:40224: EOF
I0903 16:30:08.632922       1 log.go:245] http: TLS handshake error from 162.253.55.55:40228: EOF