W0731 21:27:32.476961       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0731 21:27:32.481545       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"
I0731 21:27:32.482195       1 server.go:152] "listening for insecure healthz connections" logger="cert-manager.webhook" address=6080
I0731 21:27:32.482402       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/mutate"
I0731 21:27:32.482520       1 server.go:183] "Registering webhook" logger="cert-manager.controller-runtime.webhook" path="/validate"
I0731 21:27:32.482680       1 server.go:191] "Starting webhook server" logger="cert-manager.controller-runtime.webhook"
I0731 21:27:32.482752       1 server.go:242] "Serving webhook server" logger="cert-manager.controller-runtime.webhook" host="" port=10250
E0731 21:27:32.486936       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"
I0731 21:27:32.494259       1 reflector.go:359] Caches populated for *v1.Secret from k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232
I0731 21:27:33.488763       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"]
I0731 21:27:33.488816       1 dynamic_source.go:172] "Detected root CA rotation - regenerating serving certificates" logger="cert-manager"
I0731 21:27:33.491856       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"]
I0731 21:27:46.506205       1 log.go:245] http: TLS handshake error from 162.253.55.222:49294: EOF
I0731 21:27:46.614238       1 log.go:245] http: TLS handshake error from 162.253.55.222:49310: read tcp 10.0.0.218:10250->162.253.55.222:49310: read: connection reset by peer
I0731 21:28:13.929928       1 log.go:245] http: TLS handshake error from 162.253.55.222:34966: EOF
I0731 21:28:14.298219       1 log.go:245] http: TLS handshake error from 162.253.55.222:34968: EOF
I0731 21:32:29.530280       1 log.go:245] http: TLS handshake error from 162.253.55.222:55922: EOF
I0731 21:33:41.727694       1 log.go:245] http: TLS handshake error from 162.253.55.222:43798: EOF
I0731 21:34:26.998083       1 log.go:245] http: TLS handshake error from 162.253.55.222:40418: EOF
I0731 21:34:27.022562       1 log.go:245] http: TLS handshake error from 162.253.55.222:40452: read tcp 10.0.0.218:10250->162.253.55.222:40452: read: connection reset by peer
I0731 21:34:27.023442       1 log.go:245] http: TLS handshake error from 162.253.55.222:40460: EOF
I0731 21:38:26.640007       1 log.go:245] http: TLS handshake error from 162.253.55.222:37902: EOF
I0731 21:38:26.958048       1 log.go:245] http: TLS handshake error from 162.253.55.222:37916: EOF
I0731 21:41:06.259830       1 log.go:245] http: TLS handshake error from 162.253.55.222:47172: EOF
I0731 21:42:18.555059       1 log.go:245] http: TLS handshake error from 162.253.55.222:47718: EOF
I0731 21:45:26.053987       1 log.go:245] http: TLS handshake error from 162.253.55.222:38900: EOF
I0731 21:53:27.614304       1 log.go:245] http: TLS handshake error from 162.253.55.222:60382: EOF
I0731 21:53:27.967432       1 log.go:245] http: TLS handshake error from 162.253.55.222:60402: EOF
I0731 21:55:08.212539       1 log.go:245] http: TLS handshake error from 162.253.55.222:53086: EOF
I0731 21:56:06.579751       1 log.go:245] http: TLS handshake error from 162.253.55.222:59206: EOF
I0731 22:03:03.450586       1 log.go:245] http: TLS handshake error from 162.253.55.222:34920: EOF
I0731 22:04:10.077577       1 log.go:245] http: TLS handshake error from 162.253.55.222:42972: read tcp 10.0.0.218:10250->162.253.55.222:42972: read: connection reset by peer
I0731 22:04:10.358517       1 log.go:245] http: TLS handshake error from 162.253.55.222:53938: read tcp 10.0.0.218:10250->162.253.55.222:53938: read: connection reset by peer
I0731 22:08:08.629117       1 log.go:245] http: TLS handshake error from 162.253.55.222:46998: EOF
I0731 22:10:28.371825       1 log.go:245] http: TLS handshake error from 162.253.55.222:42452: EOF
I0731 22:13:03.064277       1 log.go:245] http: TLS handshake error from 162.253.55.222:47212: EOF
I0731 22:13:03.445178       1 log.go:245] http: TLS handshake error from 162.253.55.222:47240: read tcp 10.0.0.218:10250->162.253.55.222:47240: read: connection reset by peer
I0731 22:13:51.195497       1 log.go:245] http: TLS handshake error from 162.253.55.222:60918: EOF
I0731 22:13:52.160536       1 log.go:245] http: TLS handshake error from 162.253.55.222:60922: EOF
I0731 22:13:52.694115       1 log.go:245] http: TLS handshake error from 162.253.55.222:60926: EOF
I0731 22:13:53.272877       1 log.go:245] http: TLS handshake error from 162.253.55.222:60942: EOF
I0731 22:17:31.263655       1 log.go:245] http: TLS handshake error from 162.253.55.222:37790: EOF
I0731 22:17:31.810508       1 log.go:245] http: TLS handshake error from 162.253.55.222:37798: EOF
I0731 22:17:33.939480       1 log.go:245] http: TLS handshake error from 162.253.55.222:37810: EOF
I0731 22:17:34.409199       1 log.go:245] http: TLS handshake error from 162.253.55.222:37826: EOF