W0706 21:20:51.529900       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0706 21:20:51.531762       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"
I0706 21:20:51.532053       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0706 21:20:51.532146       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0706 21:20:51.532213       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0706 21:20:51.532250       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0706 21:20:51.535196       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0706 21:20:51.538579       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"
I0706 21:20:51.541155       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0706 21:20:52.536227       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"]
I0706 21:20:52.536303       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0706 21:20:52.538526       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"]
I0706 21:21:07.685780       1 log.go:245] http: TLS handshake error from 199.204.45.72:57450: EOF
I0706 21:21:07.687270       1 log.go:245] http: TLS handshake error from 199.204.45.72:57456: EOF
I0706 21:21:07.699756       1 log.go:245] http: TLS handshake error from 199.204.45.72:57460: EOF
I0706 21:21:07.791029       1 log.go:245] http: TLS handshake error from 199.204.45.72:57480: EOF
I0706 21:21:07.806085       1 log.go:245] http: TLS handshake error from 199.204.45.72:57490: EOF
I0706 21:21:35.400378       1 log.go:245] http: TLS handshake error from 199.204.45.72:48872: EOF
I0706 21:25:47.936204       1 log.go:245] http: TLS handshake error from 199.204.45.72:54726: EOF
I0706 21:26:54.565059       1 log.go:245] http: TLS handshake error from 199.204.45.72:34330: EOF
I0706 21:26:54.565116       1 log.go:245] http: TLS handshake error from 199.204.45.72:34340: EOF
I0706 21:26:54.587608       1 log.go:245] http: TLS handshake error from 199.204.45.72:34348: EOF
I0706 21:27:40.833945       1 log.go:245] http: TLS handshake error from 199.204.45.72:37030: EOF
I0706 21:31:13.274064       1 log.go:245] http: TLS handshake error from 199.204.45.72:60916: EOF
I0706 21:31:55.999361       1 log.go:245] http: TLS handshake error from 199.204.45.72:58670: read tcp 10.0.0.2:10250->199.204.45.72:58670: read: connection reset by peer
I0706 21:31:56.476267       1 log.go:245] http: TLS handshake error from 199.204.45.72:58678: EOF