W0729 00:50:04.610053       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0729 00:50:04.613293       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"
I0729 00:50:04.613809       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0729 00:50:04.613955       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0729 00:50:04.614053       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0729 00:50:04.614099       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0729 00:50:04.614142       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0729 00:50:04.620550       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"
I0729 00:50:04.622598       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0729 00:50:05.620806       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"]
I0729 00:50:05.620856       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0729 00:50:05.624028       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"]
I0729 00:50:17.081017       1 log.go:245] http: TLS handshake error from 199.204.45.238:53548: EOF
I0729 00:50:17.081867       1 log.go:245] http: TLS handshake error from 199.204.45.238:53552: EOF
I0729 00:50:44.517164       1 log.go:245] http: TLS handshake error from 199.204.45.238:34100: EOF
I0729 00:50:44.521394       1 log.go:245] http: TLS handshake error from 199.204.45.238:34110: EOF
I0729 00:50:44.746093       1 log.go:245] http: TLS handshake error from 199.204.45.238:34120: EOF
I0729 00:54:41.849919       1 log.go:245] http: TLS handshake error from 199.204.45.238:37626: EOF
I0729 00:54:41.864060       1 log.go:245] http: TLS handshake error from 199.204.45.238:37638: EOF
I0729 00:55:46.626697       1 log.go:245] http: TLS handshake error from 199.204.45.238:50696: EOF
I0729 00:56:32.237530       1 log.go:245] http: TLS handshake error from 199.204.45.238:48624: EOF
I0729 00:56:32.794120       1 log.go:245] http: TLS handshake error from 199.204.45.238:48656: EOF
I0729 01:00:24.356694       1 log.go:245] http: TLS handshake error from 199.204.45.238:55636: EOF
I0729 01:00:24.374630       1 log.go:245] http: TLS handshake error from 199.204.45.238:55648: EOF
I0729 01:01:14.229098       1 log.go:245] http: TLS handshake error from 199.204.45.238:51972: EOF
I0729 01:01:14.579269       1 log.go:245] http: TLS handshake error from 199.204.45.238:51986: read tcp 10.0.0.79:10250->199.204.45.238:51986: read: connection reset by peer
I0729 01:01:14.599861       1 log.go:245] http: TLS handshake error from 199.204.45.238:52002: EOF