W0728 05:57:38.229499       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0728 05:57:38.233723       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"
I0728 05:57:38.234322       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0728 05:57:38.234520       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0728 05:57:38.234641       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0728 05:57:38.234737       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0728 05:57:38.234800       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0728 05:57:38.241836       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"
I0728 05:57:38.247405       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0728 05:57:39.241635       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"]
I0728 05:57:39.241705       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0728 05:57:39.245056       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"]
I0728 06:00:34.655890       1 log.go:245] http: TLS handshake error from 199.19.213.99:39196: read tcp 10.0.0.192:10250->199.19.213.99:39196: read: connection reset by peer
I0728 06:00:34.657257       1 log.go:245] http: TLS handshake error from 199.19.213.99:39210: EOF
I0728 06:00:34.669119       1 log.go:245] http: TLS handshake error from 199.19.213.99:39212: EOF
I0728 06:00:34.678050       1 log.go:245] http: TLS handshake error from 199.19.213.99:39226: EOF
I0728 06:09:37.683507       1 log.go:245] http: TLS handshake error from 199.19.213.99:35320: EOF
I0728 06:10:52.692143       1 log.go:245] http: TLS handshake error from 199.19.213.99:54442: EOF
I0728 06:11:42.052633       1 log.go:245] http: TLS handshake error from 199.19.213.99:37256: EOF
I0728 06:11:42.074745       1 log.go:245] http: TLS handshake error from 199.19.213.99:37264: EOF
I0728 06:11:42.076210       1 log.go:245] http: TLS handshake error from 199.19.213.99:37292: EOF
I0728 06:20:18.487297       1 log.go:245] http: TLS handshake error from 199.19.213.99:41260: EOF
I0728 06:33:28.449278       1 log.go:245] http: TLS handshake error from 199.19.213.99:41828: read tcp 10.0.0.192:10250->199.19.213.99:41828: read: connection reset by peer