W0717 12:35:18.135503       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0717 12:35:18.139380       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 12:35:18.139761       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0717 12:35:18.139886       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0717 12:35:18.139963       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0717 12:35:18.140026       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0717 12:35:18.140059       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0717 12:35:18.146556       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 12:35:18.150892       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0717 12:35:19.146939       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 12:35:19.147045       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0717 12:35:19.150916       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 12:35:31.625154       1 log.go:245] http: TLS handshake error from 199.19.213.238:35240: read tcp 10.0.0.5:10250->199.19.213.238:35240: read: connection reset by peer
I0717 12:35:31.626997       1 log.go:245] http: TLS handshake error from 199.19.213.238:35242: EOF
I0717 12:35:31.723064       1 log.go:245] http: TLS handshake error from 199.19.213.238:35268: EOF
I0717 12:35:57.912476       1 log.go:245] http: TLS handshake error from 199.19.213.238:49180: EOF
I0717 12:40:00.044513       1 log.go:245] http: TLS handshake error from 199.19.213.238:36656: EOF
I0717 12:41:08.332773       1 log.go:245] http: TLS handshake error from 199.19.213.238:38870: EOF
I0717 12:41:08.333977       1 log.go:245] http: TLS handshake error from 199.19.213.238:38876: EOF
I0717 12:41:08.348533       1 log.go:245] http: TLS handshake error from 199.19.213.238:38878: EOF
I0717 12:41:08.349419       1 log.go:245] http: TLS handshake error from 199.19.213.238:38884: EOF
I0717 12:41:53.828242       1 log.go:245] http: TLS handshake error from 199.19.213.238:38426: read tcp 10.0.0.5:10250->199.19.213.238:38426: read: connection reset by peer
I0717 12:45:47.033279       1 log.go:245] http: TLS handshake error from 199.19.213.238:57078: EOF