W0822 18:39:51.894403       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0822 18:39:51.897644       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"
I0822 18:39:51.898121       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0822 18:39:51.898324       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0822 18:39:51.898460       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0822 18:39:51.898535       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0822 18:39:51.898599       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0822 18:39:51.906203       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"
I0822 18:39:51.908918       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0822 18:39:52.902101       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"]
I0822 18:39:52.902141       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0822 18:39:52.904327       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"]
I0822 18:40:04.451652       1 log.go:245] http: TLS handshake error from 199.204.45.61:43574: EOF
I0822 18:44:57.848374       1 log.go:245] http: TLS handshake error from 199.204.45.61:39958: read tcp 10.0.0.178:10250->199.204.45.61:39958: read: connection reset by peer
I0822 18:46:08.583431       1 log.go:245] http: TLS handshake error from 199.204.45.61:40364: EOF
I0822 18:46:08.601419       1 log.go:245] http: TLS handshake error from 199.204.45.61:40380: read tcp 10.0.0.178:10250->199.204.45.61:40380: read: connection reset by peer
I0822 18:46:08.675698       1 log.go:245] http: TLS handshake error from 199.204.45.61:40386: EOF
I0822 18:46:57.862797       1 log.go:245] http: TLS handshake error from 199.204.45.61:51706: read tcp 10.0.0.178:10250->199.204.45.61:51706: read: connection reset by peer
I0822 18:46:57.905758       1 log.go:245] http: TLS handshake error from 199.204.45.61:51742: EOF
I0822 18:46:57.910024       1 log.go:245] http: TLS handshake error from 199.204.45.61:51722: EOF
I0822 18:51:36.201764       1 log.go:245] http: TLS handshake error from 199.204.45.61:51994: read tcp 10.0.0.178:10250->199.204.45.61:51994: read: connection reset by peer