W0726 15:46:31.664485       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0726 15:46:31.667077       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"
I0726 15:46:31.667481       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0726 15:46:31.667586       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0726 15:46:31.667673       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0726 15:46:31.667728       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0726 15:46:31.667761       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0726 15:46:31.674091       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"
I0726 15:46:31.676535       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0726 15:46:32.673885       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"]
I0726 15:46:32.674007       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0726 15:46:32.678848       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"]
I0726 15:47:04.978366       1 log.go:245] http: TLS handshake error from 199.204.45.129:60898: EOF
I0726 15:47:04.982069       1 log.go:245] http: TLS handshake error from 199.204.45.129:60902: EOF
I0726 15:53:53.358603       1 log.go:245] http: TLS handshake error from 199.204.45.129:53732: EOF
I0726 15:53:53.469646       1 log.go:245] http: TLS handshake error from 199.204.45.129:53756: read tcp 10.0.0.61:10250->199.204.45.129:53756: read: connection reset by peer
I0726 15:58:06.286221       1 log.go:245] http: TLS handshake error from 199.204.45.129:59244: read tcp 10.0.0.61:10250->199.204.45.129:59244: read: connection reset by peer
I0726 16:02:56.598603       1 log.go:245] http: TLS handshake error from 199.204.45.129:46198: EOF
I0726 16:02:56.903537       1 log.go:245] http: TLS handshake error from 199.204.45.129:46216: EOF
I0726 16:04:03.192989       1 log.go:245] http: TLS handshake error from 199.204.45.129:36592: EOF
I0726 16:04:50.670227       1 log.go:245] http: TLS handshake error from 199.204.45.129:33686: EOF
I0726 16:05:15.053898       1 log.go:245] http: TLS handshake error from 199.204.45.129:47418: read tcp 10.0.0.61:10250->199.204.45.129:47418: read: connection reset by peer
I0726 16:05:15.492803       1 log.go:245] http: TLS handshake error from 199.204.45.129:47434: EOF
I0726 16:05:16.252120       1 log.go:245] http: TLS handshake error from 199.204.45.129:47444: EOF
I0726 16:05:16.574757       1 log.go:245] http: TLS handshake error from 199.204.45.129:47454: EOF