W0814 09:12:12.296587       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0814 09:12:12.299307       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"
I0814 09:12:12.299695       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0814 09:12:12.299811       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0814 09:12:12.299871       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0814 09:12:12.299913       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0814 09:12:12.299941       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0814 09:12:12.304669       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"
I0814 09:12:12.311667       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0814 09:12:13.306499       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"]
I0814 09:12:13.306558       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0814 09:12:13.311303       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"]
I0814 09:12:30.372151       1 log.go:245] http: TLS handshake error from 199.19.213.52:38232: EOF
I0814 09:12:30.373450       1 log.go:245] http: TLS handshake error from 199.19.213.52:38246: EOF
I0814 09:12:30.385722       1 log.go:245] http: TLS handshake error from 199.19.213.52:38252: EOF
I0814 09:12:57.872870       1 log.go:245] http: TLS handshake error from 199.19.213.52:44354: EOF
I0814 09:17:08.995336       1 log.go:245] http: TLS handshake error from 199.19.213.52:35030: read tcp 10.0.0.104:10250->199.19.213.52:35030: read: connection reset by peer
I0814 09:18:19.205419       1 log.go:245] http: TLS handshake error from 199.19.213.52:56862: EOF
I0814 09:18:19.206628       1 log.go:245] http: TLS handshake error from 199.19.213.52:56860: read tcp 10.0.0.104:10250->199.19.213.52:56860: read: connection reset by peer
I0814 09:18:19.219985       1 log.go:245] http: TLS handshake error from 199.19.213.52:56878: EOF
I0814 09:19:05.507423       1 log.go:245] http: TLS handshake error from 199.19.213.52:45134: EOF
I0814 09:19:05.549641       1 log.go:245] http: TLS handshake error from 199.19.213.52:45162: EOF
I0814 09:22:42.534241       1 log.go:245] http: TLS handshake error from 199.19.213.52:58398: EOF
I0814 09:23:24.443560       1 log.go:245] http: TLS handshake error from 199.19.213.52:42348: EOF