W0624 09:06:25.332609       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0624 09:06:25.335534       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"
I0624 09:06:25.335965       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0624 09:06:25.336088       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0624 09:06:25.336182       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0624 09:06:25.336241       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0624 09:06:25.336278       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0624 09:06:25.344419       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"
I0624 09:06:25.346765       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0624 09:06:26.342617       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"]
I0624 09:06:26.342698       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0624 09:06:26.346938       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"]
I0624 09:07:26.576786       1 log.go:245] http: TLS handshake error from 199.204.45.70:49350: EOF
I0624 09:07:26.578133       1 log.go:245] http: TLS handshake error from 199.204.45.70:49364: EOF
I0624 09:12:32.324622       1 log.go:245] http: TLS handshake error from 199.204.45.70:44370: EOF
I0624 09:13:40.713701       1 log.go:245] http: TLS handshake error from 199.204.45.70:39064: read tcp 10.0.0.1:10250->199.204.45.70:39064: read: connection reset by peer
I0624 09:13:40.714241       1 log.go:245] http: TLS handshake error from 199.204.45.70:39076: read tcp 10.0.0.1:10250->199.204.45.70:39076: read: connection reset by peer
I0624 09:13:40.800577       1 log.go:245] http: TLS handshake error from 199.204.45.70:39082: EOF
I0624 09:14:31.152094       1 log.go:245] http: TLS handshake error from 199.204.45.70:35398: EOF
I0624 09:14:31.152697       1 log.go:245] http: TLS handshake error from 199.204.45.70:35400: EOF
I0624 09:14:31.198547       1 log.go:245] http: TLS handshake error from 199.204.45.70:35430: EOF
I0624 09:18:12.879510       1 log.go:245] http: TLS handshake error from 199.204.45.70:45324: read tcp 10.0.0.1:10250->199.204.45.70:45324: read: connection reset by peer
I0624 09:18:13.392678       1 log.go:245] http: TLS handshake error from 199.204.45.70:45336: read tcp 10.0.0.1:10250->199.204.45.70:45336: read: connection reset by peer
I0624 09:19:08.285991       1 log.go:245] http: TLS handshake error from 199.204.45.70:38388: EOF
I0624 09:19:09.052967       1 log.go:245] http: TLS handshake error from 199.204.45.70:38394: EOF