W0717 18:00:59.755405       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0717 18:00:59.757435       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 18:00:59.757867       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0717 18:00:59.759136       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0717 18:00:59.759363       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0717 18:00:59.759481       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0717 18:00:59.759562       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0717 18:00:59.763648       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 18:00:59.769201       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0717 18:01:00.765815       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 18:01:00.765873       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0717 18:01:00.769410       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 18:01:36.855464       1 log.go:245] http: TLS handshake error from 199.204.45.162:48576: EOF
I0717 18:01:36.856733       1 log.go:245] http: TLS handshake error from 199.204.45.162:48582: read tcp 10.0.0.104:10250->199.204.45.162:48582: read: connection reset by peer
I0717 18:05:37.735051       1 log.go:245] http: TLS handshake error from 199.204.45.162:40328: EOF
I0717 18:05:38.013746       1 log.go:245] http: TLS handshake error from 199.204.45.162:40340: EOF
I0717 18:06:46.784021       1 log.go:245] http: TLS handshake error from 199.204.45.162:58136: EOF
I0717 18:06:46.794133       1 log.go:245] http: TLS handshake error from 199.204.45.162:58148: read tcp 10.0.0.104:10250->199.204.45.162:58148: read: connection reset by peer
I0717 18:06:46.795119       1 log.go:245] http: TLS handshake error from 199.204.45.162:58150: EOF
I0717 18:06:46.864984       1 log.go:245] http: TLS handshake error from 199.204.45.162:58162: EOF
I0717 18:07:31.596692       1 log.go:245] http: TLS handshake error from 199.204.45.162:42472: EOF
I0717 18:07:31.616164       1 log.go:245] http: TLS handshake error from 199.204.45.162:42476: EOF
I0717 18:07:31.981468       1 log.go:245] http: TLS handshake error from 199.204.45.162:42500: EOF
I0717 18:11:08.250637       1 log.go:245] http: TLS handshake error from 199.204.45.162:36552: EOF
I0717 18:11:48.639363       1 log.go:245] http: TLS handshake error from 199.204.45.162:46522: read tcp 10.0.0.104:10250->199.204.45.162:46522: read: connection reset by peer