W0730 10:22:25.513393       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0730 10:22:25.515888       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"
I0730 10:22:25.516379       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0730 10:22:25.516509       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0730 10:22:25.516630       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0730 10:22:25.516677       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0730 10:22:25.516711       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0730 10:22:25.524171       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"
I0730 10:22:25.527277       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0730 10:22:26.521196       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"]
I0730 10:22:26.521277       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0730 10:22:26.524957       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"]
I0730 10:22:36.871821       1 log.go:245] http: TLS handshake error from 199.204.45.240:42932: EOF
I0730 10:22:36.875873       1 log.go:245] http: TLS handshake error from 199.204.45.240:42946: read tcp 10.0.0.6:10250->199.204.45.240:42946: read: connection reset by peer
I0730 10:23:06.106157       1 log.go:245] http: TLS handshake error from 199.204.45.240:49282: EOF
I0730 10:23:06.108042       1 log.go:245] http: TLS handshake error from 199.204.45.240:49292: EOF
I0730 10:23:06.358147       1 log.go:245] http: TLS handshake error from 199.204.45.240:49298: EOF
I0730 10:27:21.007895       1 log.go:245] http: TLS handshake error from 199.204.45.240:60098: read tcp 10.0.0.6:10250->199.204.45.240:60098: read: connection reset by peer
I0730 10:28:32.084917       1 log.go:245] http: TLS handshake error from 199.204.45.240:60916: EOF
I0730 10:28:32.089251       1 log.go:245] http: TLS handshake error from 199.204.45.240:60918: EOF
I0730 10:28:32.102338       1 log.go:245] http: TLS handshake error from 199.204.45.240:60932: EOF
I0730 10:28:32.172671       1 log.go:245] http: TLS handshake error from 199.204.45.240:60946: EOF
I0730 10:33:09.449976       1 log.go:245] http: TLS handshake error from 199.204.45.240:59268: read tcp 10.0.0.6:10250->199.204.45.240:59268: read: connection reset by peer
I0730 10:33:54.436575       1 log.go:245] http: TLS handshake error from 199.204.45.240:45640: read tcp 10.0.0.6:10250->199.204.45.240:45640: read: connection reset by peer
I0730 10:33:54.605564       1 log.go:245] http: TLS handshake error from 199.204.45.240:45644: EOF