W0416 16:48:37.945797       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0416 16:48:37.949097       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"
I0416 16:48:37.949571       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0416 16:48:37.949688       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0416 16:48:37.949817       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0416 16:48:37.949879       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0416 16:48:37.949925       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0416 16:48:37.957578       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"
I0416 16:48:37.962560       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0416 16:48:38.956470       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"]
I0416 16:48:38.956567       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0416 16:48:38.960920       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"]
I0416 16:48:51.801362       1 log.go:245] http: TLS handshake error from 199.204.45.156:43796: EOF
I0416 16:48:51.828900       1 log.go:245] http: TLS handshake error from 199.204.45.156:43798: EOF
I0416 16:48:51.842113       1 log.go:245] http: TLS handshake error from 199.204.45.156:43808: EOF
I0416 16:51:30.691262       1 log.go:245] http: TLS handshake error from 199.204.45.156:51830: EOF
I0416 16:51:30.692387       1 log.go:245] http: TLS handshake error from 199.204.45.156:51840: read tcp 10.0.0.115:10250->199.204.45.156:51840: read: connection reset by peer
I0416 16:51:30.701896       1 log.go:245] http: TLS handshake error from 199.204.45.156:51842: EOF
I0416 16:51:30.703419       1 log.go:245] http: TLS handshake error from 199.204.45.156:51848: EOF
I0416 16:51:30.712217       1 log.go:245] http: TLS handshake error from 199.204.45.156:51856: EOF
I0416 16:51:30.981372       1 log.go:245] http: TLS handshake error from 199.204.45.156:51878: read tcp 10.0.0.115:10250->199.204.45.156:51878: read: connection reset by peer
I0416 16:51:35.752974       1 log.go:245] http: TLS handshake error from 199.204.45.156:51892: EOF
I0416 16:54:18.758427       1 log.go:245] http: TLS handshake error from 199.204.45.156:33026: EOF
I0416 16:54:18.981624       1 log.go:245] http: TLS handshake error from 199.204.45.156:33050: EOF