W0731 12:36:40.548751       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0731 12:36:40.552172       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"
I0731 12:36:40.552733       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0731 12:36:40.552900       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0731 12:36:40.553008       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0731 12:36:40.553106       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0731 12:36:40.553147       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0731 12:36:40.559248       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"
I0731 12:36:40.563163       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0731 12:36:41.558681       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"]
I0731 12:36:41.558738       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0731 12:36:41.563627       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"]
I0731 12:36:58.635972       1 log.go:245] http: TLS handshake error from 199.19.213.185:47574: EOF
I0731 12:37:32.051465       1 log.go:245] http: TLS handshake error from 199.19.213.185:57196: read tcp 10.0.0.129:10250->199.19.213.185:57196: read: connection reset by peer
I0731 12:37:32.115057       1 log.go:245] http: TLS handshake error from 199.19.213.185:57208: EOF
I0731 12:37:33.196145       1 log.go:245] http: TLS handshake error from 199.19.213.185:57214: EOF
I0731 12:37:33.216782       1 log.go:245] http: TLS handshake error from 199.19.213.185:57228: EOF
I0731 12:42:28.780112       1 log.go:245] http: TLS handshake error from 199.19.213.185:36814: EOF
I0731 12:43:31.932379       1 log.go:245] http: TLS handshake error from 199.19.213.185:60858: read tcp 10.0.0.129:10250->199.19.213.185:60858: read: connection reset by peer
I0731 12:43:31.933524       1 log.go:245] http: TLS handshake error from 199.19.213.185:60870: EOF
I0731 12:44:19.777666       1 log.go:245] http: TLS handshake error from 199.19.213.185:50898: EOF
I0731 12:44:19.835074       1 log.go:245] http: TLS handshake error from 199.19.213.185:50908: EOF
I0731 12:44:20.243145       1 log.go:245] http: TLS handshake error from 199.19.213.185:50916: read tcp 10.0.0.129:10250->199.19.213.185:50916: read: connection reset by peer
I0731 12:48:14.356791       1 log.go:245] http: TLS handshake error from 199.19.213.185:58686: EOF
I0731 12:48:14.943583       1 log.go:245] http: TLS handshake error from 199.19.213.185:58708: EOF