W0814 08:59:24.368690       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0814 08:59:24.373377       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 08:59:24.373988       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0814 08:59:24.374099       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0814 08:59:24.374188       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0814 08:59:24.374253       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0814 08:59:24.374298       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0814 08:59:24.381292       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 08:59:24.387758       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0814 08:59:25.380135       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 08:59:25.380223       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0814 08:59:25.385465       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 08:59:42.645256       1 log.go:245] http: TLS handshake error from 199.19.213.82:53788: EOF
I0814 08:59:42.645874       1 log.go:245] http: TLS handshake error from 199.19.213.82:53798: read tcp 10.0.0.132:10250->199.19.213.82:53798: read: connection reset by peer
I0814 08:59:42.658476       1 log.go:245] http: TLS handshake error from 199.19.213.82:53814: EOF
I0814 09:00:10.352925       1 log.go:245] http: TLS handshake error from 199.19.213.82:39678: EOF
I0814 09:00:10.562287       1 log.go:245] http: TLS handshake error from 199.19.213.82:39682: read tcp 10.0.0.132:10250->199.19.213.82:39682: read: connection reset by peer
I0814 09:06:45.383115       1 log.go:245] http: TLS handshake error from 199.19.213.82:60128: read tcp 10.0.0.132:10250->199.19.213.82:60128: read: connection reset by peer
I0814 09:06:45.442521       1 log.go:245] http: TLS handshake error from 199.19.213.82:60154: EOF
I0814 09:06:45.442618       1 log.go:245] http: TLS handshake error from 199.19.213.82:60138: read tcp 10.0.0.132:10250->199.19.213.82:60138: read: connection reset by peer
I0814 09:06:45.443139       1 log.go:245] http: TLS handshake error from 199.19.213.82:60170: EOF
I0814 09:10:32.779338       1 log.go:245] http: TLS handshake error from 199.19.213.82:57832: EOF
I0814 09:10:33.022004       1 log.go:245] http: TLS handshake error from 199.19.213.82:57836: EOF
I0814 09:11:18.464067       1 log.go:245] http: TLS handshake error from 199.19.213.82:52840: EOF