W0717 05:31:26.137261       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0717 05:31:26.139677       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 05:31:26.140069       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0717 05:31:26.140173       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0717 05:31:26.140259       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0717 05:31:26.140317       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0717 05:31:26.140351       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0717 05:31:26.147610       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 05:31:26.150215       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0717 05:31:27.147173       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 05:31:27.147219       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0717 05:31:27.150491       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 05:31:44.441312       1 log.go:245] http: TLS handshake error from 199.204.45.4:33672: read tcp 10.0.0.28:10250->199.204.45.4:33672: read: connection reset by peer
I0717 05:31:44.553443       1 log.go:245] http: TLS handshake error from 199.204.45.4:33686: read tcp 10.0.0.28:10250->199.204.45.4:33686: read: connection reset by peer
I0717 05:34:05.091324       1 log.go:245] http: TLS handshake error from 199.204.45.4:39916: EOF
I0717 05:34:05.200180       1 log.go:245] http: TLS handshake error from 199.204.45.4:39932: EOF
I0717 05:34:05.201006       1 log.go:245] http: TLS handshake error from 199.204.45.4:39930: EOF
I0717 05:34:05.202540       1 log.go:245] http: TLS handshake error from 199.204.45.4:39944: EOF
I0717 05:34:05.481593       1 log.go:245] http: TLS handshake error from 199.204.45.4:39966: EOF
I0717 05:34:05.828582       1 log.go:245] http: TLS handshake error from 199.204.45.4:39968: EOF
I0717 05:34:05.852728       1 log.go:245] http: TLS handshake error from 199.204.45.4:39984: EOF
I0717 05:34:12.561027       1 log.go:245] http: TLS handshake error from 199.204.45.4:40000: EOF
I0717 05:34:12.563181       1 log.go:245] http: TLS handshake error from 199.204.45.4:40006: EOF