W0702 19:37:44.110674       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0702 19:37:44.114493       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"
I0702 19:37:44.115068       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0702 19:37:44.115269       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0702 19:37:44.115416       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0702 19:37:44.115501       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0702 19:37:44.115558       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0702 19:37:44.124657       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"
I0702 19:37:44.128734       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0702 19:37:45.122637       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"]
I0702 19:37:45.122698       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0702 19:37:45.126603       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"]
I0702 19:38:01.936301       1 log.go:245] http: TLS handshake error from 199.204.45.238:36142: read tcp 10.0.0.193:10250->199.204.45.238:36142: read: connection reset by peer
I0702 19:38:01.938185       1 log.go:245] http: TLS handshake error from 199.204.45.238:36152: EOF
I0702 19:38:01.950038       1 log.go:245] http: TLS handshake error from 199.204.45.238:36156: EOF
I0702 19:38:55.033048       1 log.go:245] http: TLS handshake error from 199.204.45.238:38478: EOF
I0702 19:38:55.034215       1 log.go:245] http: TLS handshake error from 199.204.45.238:38484: EOF
I0702 19:43:57.720821       1 log.go:245] http: TLS handshake error from 199.204.45.238:55110: EOF
I0702 19:45:04.012075       1 log.go:245] http: TLS handshake error from 199.204.45.238:49768: read tcp 10.0.0.193:10250->199.204.45.238:49768: read: connection reset by peer
I0702 19:46:00.411544       1 log.go:245] http: TLS handshake error from 199.204.45.238:48718: EOF
I0702 19:46:00.437416       1 log.go:245] http: TLS handshake error from 199.204.45.238:48738: read tcp 10.0.0.193:10250->199.204.45.238:48738: read: connection reset by peer
I0702 19:46:00.437464       1 log.go:245] http: TLS handshake error from 199.204.45.238:48750: EOF
I0702 19:46:00.438744       1 log.go:245] http: TLS handshake error from 199.204.45.238:48760: EOF
I0702 19:50:25.967795       1 log.go:245] http: TLS handshake error from 199.204.45.238:53302: EOF
I0702 19:51:12.907374       1 log.go:245] http: TLS handshake error from 199.204.45.238:33528: EOF