W0717 15:52:06.733685       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0717 15:52:06.737278       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 15:52:06.737827       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0717 15:52:06.737964       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0717 15:52:06.738084       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0717 15:52:06.738157       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0717 15:52:06.738205       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0717 15:52:06.744599       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 15:52:06.746897       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0717 15:52:07.743717       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 15:52:07.743772       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0717 15:52:07.749093       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 15:52:54.377004       1 log.go:245] http: TLS handshake error from 199.19.213.48:51320: EOF
I0717 15:52:54.377105       1 log.go:245] http: TLS handshake error from 199.19.213.48:51332: read tcp 10.0.0.212:10250->199.19.213.48:51332: read: connection reset by peer
I0717 15:58:35.212967       1 log.go:245] http: TLS handshake error from 199.19.213.48:59660: EOF
I0717 15:58:35.418851       1 log.go:245] http: TLS handshake error from 199.19.213.48:59690: read tcp 10.0.0.212:10250->199.19.213.48:59690: read: connection reset by peer
I0717 16:05:57.720393       1 log.go:245] http: TLS handshake error from 199.19.213.48:47852: EOF
I0717 16:05:57.721331       1 log.go:245] http: TLS handshake error from 199.19.213.48:47856: EOF
I0717 16:06:44.826514       1 log.go:245] http: TLS handshake error from 199.19.213.48:47130: EOF
I0717 16:06:44.837949       1 log.go:245] http: TLS handshake error from 199.19.213.48:47142: EOF
I0717 16:06:44.870672       1 log.go:245] http: TLS handshake error from 199.19.213.48:47164: EOF
I0717 16:11:20.227803       1 log.go:245] http: TLS handshake error from 199.19.213.48:55200: EOF
I0717 16:11:20.463363       1 log.go:245] http: TLS handshake error from 199.19.213.48:55208: read tcp 10.0.0.212:10250->199.19.213.48:55208: read: connection reset by peer