W0714 16:50:17.474807       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0714 16:50:17.477315       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"
I0714 16:50:17.477933       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0714 16:50:17.478037       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0714 16:50:17.478119       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0714 16:50:17.478168       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0714 16:50:17.478204       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0714 16:50:17.485359       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"
I0714 16:50:17.486335       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0714 16:50:18.484391       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"]
I0714 16:50:18.484458       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0714 16:50:18.488267       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"]
I0714 16:50:30.469705       1 log.go:245] http: TLS handshake error from 199.204.45.205:36288: EOF
I0714 16:50:30.556409       1 log.go:245] http: TLS handshake error from 199.204.45.205:36316: EOF
I0714 16:50:57.273640       1 log.go:245] http: TLS handshake error from 199.204.45.205:48396: EOF
I0714 16:50:57.478157       1 log.go:245] http: TLS handshake error from 199.204.45.205:48408: read tcp 10.0.0.155:10250->199.204.45.205:48408: read: connection reset by peer
I0714 16:56:47.589847       1 log.go:245] http: TLS handshake error from 199.204.45.205:50876: read tcp 10.0.0.155:10250->199.204.45.205:50876: read: connection reset by peer
I0714 17:00:26.286147       1 log.go:245] http: TLS handshake error from 199.204.45.205:45986: read tcp 10.0.0.155:10250->199.204.45.205:45986: read: connection reset by peer
I0714 17:00:26.595967       1 log.go:245] http: TLS handshake error from 199.204.45.205:46004: EOF
I0714 17:00:26.613586       1 log.go:245] http: TLS handshake error from 199.204.45.205:46012: EOF
I0714 17:01:14.602305       1 log.go:245] http: TLS handshake error from 199.204.45.205:37548: read tcp 10.0.0.155:10250->199.204.45.205:37548: read: connection reset by peer
I0714 17:01:14.897745       1 log.go:245] http: TLS handshake error from 199.204.45.205:47844: EOF