consul pod failing, how to fix that?

uday

11/20/22, 6:57 PM

I have installed consul by following steps in the link

Only change is I ran all the configuration in a new namespace (consul) instead of default.

After that, I got below error when I checked pods.

kubectl get pods -n consul

NAME                                                          READY   STATUS             RESTARTS   AGE
consul-8pqwf                                                  1/1     Running            0          10m
consul-connect-injector-webhook-deployment-7db46fbcd8-7njgx   0/1     CrashLoopBackOff   2          24s
consul-controller-5788b8f6c7-dp54h                            1/1     Running            0          10m
consul-server-0                                               1/1     Running            0          10m
consul-webhook-cert-manager-cfbb689f7-94wv8                   1/1     Running            0          10m
grafana-dbb8fd8-zfwhr                                         1/1     Running            0          10m
prometheus-server-5cbddcc44b-wsnhh                            2/2     Running            0          10m

kubectl logs consul-connect-injector-webhook-deployment-7db46fbcd8-7njgx -n consul
Listening on ":8080"...
2021/07/20 18:55:21 http: TLS handshake error from 10.244.0.1:43248: No certificate available.
2021/07/20 18:55:21 http: TLS handshake error from 10.244.0.1:43246: No certificate available.
Error loading TLS keypair: tls: failed to find any PEM data in certificate input
Error loading TLS keypair: tls: failed to find any PEM data in certificate input
2021/07/20 18:55:23 http: TLS handshake error from 10.244.0.1:43288: No certificate available.
2021/07/20 18:55:23 http: TLS handshake error from 10.244.0.1:43286: No certificate available.
terminated received, shutting down
Updated certificate bundle received. Updating certs...
2021/07/20 18:55:23 [ERROR] helper/cert: error loading next cert: context canceled

How to rectify this?

0 + 0

consul