W0619 00:10:54.174542       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0619 00:10:54.177100       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"
I0619 00:10:54.177500       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0619 00:10:54.177609       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0619 00:10:54.177694       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0619 00:10:54.177772       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0619 00:10:54.177807       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0619 00:10:54.182350       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"
I0619 00:10:54.188836       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0619 00:10:55.183487       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"]
I0619 00:10:55.183546       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0619 00:10:55.187907       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"]
I0619 00:11:12.046630       1 log.go:245] http: TLS handshake error from 199.204.45.116:50468: EOF
I0619 00:11:12.059851       1 log.go:245] http: TLS handshake error from 199.204.45.116:50480: EOF
I0619 00:11:12.060039       1 log.go:245] http: TLS handshake error from 199.204.45.116:50484: read tcp 10.0.0.152:10250->199.204.45.116:50484: read: connection reset by peer
I0619 00:11:39.385131       1 log.go:245] http: TLS handshake error from 199.204.45.116:36778: EOF
I0619 00:16:31.216796       1 log.go:245] http: TLS handshake error from 199.204.45.116:53660: read tcp 10.0.0.152:10250->199.204.45.116:53660: read: connection reset by peer
I0619 00:16:31.403350       1 log.go:245] http: TLS handshake error from 199.204.45.116:53682: EOF
I0619 00:17:36.291305       1 log.go:245] http: TLS handshake error from 199.204.45.116:46030: EOF
I0619 00:17:36.745654       1 log.go:245] http: TLS handshake error from 199.204.45.116:46034: EOF
I0619 00:17:36.757416       1 log.go:245] http: TLS handshake error from 199.204.45.116:46042: EOF
I0619 00:18:23.272349       1 log.go:245] http: TLS handshake error from 199.204.45.116:60802: EOF
I0619 00:18:23.273839       1 log.go:245] http: TLS handshake error from 199.204.45.116:60816: EOF
I0619 00:22:13.863008       1 log.go:245] http: TLS handshake error from 199.204.45.116:44974: EOF