W0717 13:42:40.684183       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0717 13:42:40.686849       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 13:42:40.687271       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0717 13:42:40.687370       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0717 13:42:40.687430       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0717 13:42:40.687470       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0717 13:42:40.687506       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0717 13:42:40.695113       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 13:42:40.698185       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0717 13:42:41.691525       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 13:42:41.691570       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0717 13:42:41.694722       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 13:42:52.190517       1 log.go:245] http: TLS handshake error from 199.204.45.227:41728: EOF
I0717 13:42:52.207262       1 log.go:245] http: TLS handshake error from 199.204.45.227:41740: EOF
I0717 13:42:52.300116       1 log.go:245] http: TLS handshake error from 199.204.45.227:41764: read tcp 10.0.0.14:10250->199.204.45.227:41764: read: connection reset by peer
I0717 13:43:26.652325       1 log.go:245] http: TLS handshake error from 199.204.45.227:40046: read tcp 10.0.0.14:10250->199.204.45.227:40046: read: connection reset by peer
I0717 13:43:26.664796       1 log.go:245] http: TLS handshake error from 199.204.45.227:40058: read tcp 10.0.0.14:10250->199.204.45.227:40058: read: connection reset by peer
I0717 13:43:26.665994       1 log.go:245] http: TLS handshake error from 199.204.45.227:40064: read tcp 10.0.0.14:10250->199.204.45.227:40064: read: connection reset by peer
I0717 13:43:26.666703       1 log.go:245] http: TLS handshake error from 199.204.45.227:40070: EOF
I0717 13:43:26.667308       1 log.go:245] http: TLS handshake error from 199.204.45.227:40082: EOF
I0717 13:48:37.684147       1 log.go:245] http: TLS handshake error from 199.204.45.227:60616: EOF
I0717 13:55:36.327782       1 log.go:245] http: TLS handshake error from 199.204.45.227:39184: EOF
I0717 13:55:36.407991       1 log.go:245] http: TLS handshake error from 199.204.45.227:39208: EOF
I0717 13:56:24.282699       1 log.go:245] http: TLS handshake error from 199.204.45.227:35026: EOF
I0717 13:56:24.304231       1 log.go:245] http: TLS handshake error from 199.204.45.227:35032: EOF
I0717 13:56:24.306913       1 log.go:245] http: TLS handshake error from 199.204.45.227:35038: EOF
I0717 13:56:24.307136       1 log.go:245] http: TLS handshake error from 199.204.45.227:35046: EOF