W0717 10:46:01.119270       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0717 10:46:01.122805       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 10:46:01.123487       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0717 10:46:01.123829       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0717 10:46:01.124126       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0717 10:46:01.124315       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0717 10:46:01.124458       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0717 10:46:01.133760       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 10:46:01.135655       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0717 10:46:02.128182       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 10:46:02.128226       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0717 10:46:02.131326       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 10:46:15.149187       1 log.go:245] http: TLS handshake error from 199.204.45.222:60422: EOF
I0717 10:46:15.279159       1 log.go:245] http: TLS handshake error from 199.204.45.222:60434: EOF
I0717 10:46:45.063898       1 log.go:245] http: TLS handshake error from 199.204.45.222:44604: read tcp 10.0.0.42:10250->199.204.45.222:44604: read: connection reset by peer
I0717 10:52:33.789150       1 log.go:245] http: TLS handshake error from 199.204.45.222:39910: EOF
I0717 10:52:33.917074       1 log.go:245] http: TLS handshake error from 199.204.45.222:39924: EOF
I0717 10:53:24.989773       1 log.go:245] http: TLS handshake error from 199.204.45.222:39978: EOF
I0717 10:53:25.036077       1 log.go:245] http: TLS handshake error from 199.204.45.222:39986: EOF
I0717 10:53:25.045697       1 log.go:245] http: TLS handshake error from 199.204.45.222:40018: EOF
I0717 10:57:18.572852       1 log.go:245] http: TLS handshake error from 199.204.45.222:53340: EOF
I0717 10:57:18.867373       1 log.go:245] http: TLS handshake error from 199.204.45.222:53360: EOF
I0717 10:58:07.783636       1 log.go:245] http: TLS handshake error from 199.204.45.222:55086: EOF
I0717 10:58:08.150899       1 log.go:245] http: TLS handshake error from 199.204.45.222:55100: EOF