W0717 09:03:08.466738       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0717 09:03:08.470969       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 09:03:08.471711       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0717 09:03:08.471886       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0717 09:03:08.472043       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0717 09:03:08.472185       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0717 09:03:08.472259       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0717 09:03:08.479122       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 09:03:08.482388       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0717 09:03:09.477818       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 09:03:09.477862       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0717 09:03:09.481763       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 09:03:23.627559       1 log.go:245] http: TLS handshake error from 199.204.45.4:50014: EOF
I0717 09:03:56.332696       1 log.go:245] http: TLS handshake error from 199.204.45.4:51170: EOF
I0717 09:09:13.577525       1 log.go:245] http: TLS handshake error from 199.204.45.4:44082: EOF
I0717 09:10:24.202926       1 log.go:245] http: TLS handshake error from 199.204.45.4:51702: EOF
I0717 09:10:24.203877       1 log.go:245] http: TLS handshake error from 199.204.45.4:51718: EOF
I0717 09:10:24.287982       1 log.go:245] http: TLS handshake error from 199.204.45.4:51728: EOF
I0717 09:11:11.897416       1 log.go:245] http: TLS handshake error from 199.204.45.4:33226: EOF
I0717 09:11:11.898346       1 log.go:245] http: TLS handshake error from 199.204.45.4:33236: read tcp 10.0.0.21:10250->199.204.45.4:33236: read: connection reset by peer
I0717 09:11:11.902797       1 log.go:245] http: TLS handshake error from 199.204.45.4:33208: EOF
I0717 09:15:14.894018       1 log.go:245] http: TLS handshake error from 199.204.45.4:45090: EOF
I0717 09:16:01.723785       1 log.go:245] http: TLS handshake error from 199.204.45.4:38430: EOF
I0717 09:16:02.143500       1 log.go:245] http: TLS handshake error from 199.204.45.4:38444: EOF