W0402 16:44:37.716510       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0402 16:44:37.719572       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"
I0402 16:44:37.719978       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0402 16:44:37.720088       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0402 16:44:37.720183       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0402 16:44:37.720245       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0402 16:44:37.720289       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0402 16:44:37.727109       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"
I0402 16:44:37.733126       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0402 16:44:38.727757       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"]
I0402 16:44:38.727826       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0402 16:44:38.731679       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"]
I0402 16:44:52.117298       1 log.go:245] http: TLS handshake error from 199.204.45.140:38648: read tcp 10.0.0.254:10250->199.204.45.140:38648: read: connection reset by peer
I0402 16:44:52.118214       1 log.go:245] http: TLS handshake error from 199.204.45.140:38660: read tcp 10.0.0.254:10250->199.204.45.140:38660: read: connection reset by peer
I0402 16:44:52.130881       1 log.go:245] http: TLS handshake error from 199.204.45.140:38664: EOF
I0402 16:44:52.229491       1 log.go:245] http: TLS handshake error from 199.204.45.140:38682: read tcp 10.0.0.254:10250->199.204.45.140:38682: read: connection reset by peer
I0402 16:45:24.757318       1 log.go:245] http: TLS handshake error from 199.204.45.140:38460: read tcp 10.0.0.254:10250->199.204.45.140:38460: read: connection reset by peer
I0402 16:45:25.552212       1 log.go:245] http: TLS handshake error from 199.204.45.140:38464: read tcp 10.0.0.254:10250->199.204.45.140:38464: read: connection reset by peer
I0402 16:47:55.821547       1 log.go:245] http: TLS handshake error from 199.204.45.140:41250: EOF
I0402 16:47:55.823794       1 log.go:245] http: TLS handshake error from 199.204.45.140:41254: EOF
I0402 16:50:37.652378       1 log.go:245] http: TLS handshake error from 199.204.45.140:51420: EOF
I0402 16:50:37.842197       1 log.go:245] http: TLS handshake error from 199.204.45.140:51432: EOF
I0402 16:51:52.225759       1 log.go:245] http: TLS handshake error from 199.204.45.140:44344: EOF
I0402 16:52:48.671652       1 log.go:245] http: TLS handshake error from 199.204.45.140:51116: EOF
I0402 16:53:04.915338       1 log.go:245] http: TLS handshake error from 199.204.45.140:55906: EOF
I0402 16:59:20.767495       1 log.go:245] http: TLS handshake error from 199.204.45.140:33092: EOF