Consul-connect-injector and consul-server-acl-init pod getting erorr

Consul
1

NAME READY STATUS RESTARTS AGE
consul-connect-injector-579d854b8c-24xqn 0/1 Running 5 (58s ago) 8m25s
consul-connect-injector-75bbb95d86-dfqm7 0/1 Running 6 (2m15s ago) 8m10s
consul-server-0 1/1 Running 0 64m
consul-server-1 1/1 Running 0 50m
consul-server-2 1/1 Running 0 49m
consul-server-acl-init-g5bhj 0/1 Error 0 3h40m
consul-server-acl-init-jf5jn 0/1 Error 0 154m
consul-server-acl-init-n6n4f 0/1 Error 0 3h55m
consul-server-acl-init-s75tr 0/1 Error 0 3h9m
consul-server-acl-init-sk54k 0/1 Error 0 3h25m
consul-server-acl-init-xcvc6 0/1 Error 0 172m
consul-webhook-cert-manager-f4988cf75-hrzfm 1/1 Running 0 3h55m

erorr:

  1. 2023-09-16T12:53:36.746Z [ERROR] consul-server-connection-manager: connection error: error=“rpc error: code = InvalidArgument desc = auth method "consul-k8s-component-auth-method" not found”
    unable to start Consul server watcher: context canceled
    2023-09-16T12:53:43.366Z [INFO] consul-server-connection-manager: stopping

2023-09-16T10:18:14.897Z [ERROR] Error resolving IP Address: err=“failed to resolve DNS name: consul-server.consul.svc: lookup consul-server.consul.svc: i/o timeout”
2023-09-16T10:18:24.925Z [ERROR] Error resolving IP Address: err=“failed to resolve DNS name: consul-server.consul.svc: lookup consul-server.consul.svc: i/o timeout”
2023-09-16T10:18:36.202Z [ERROR] Error resolving IP Address: err=“failed to resolve DNS name: consul-server.consul.svc: lookup consul-server.consul.svc: i/o timeout”
failed to resolve DNS name: consul-server.consul.svc: lookup consul-server.consul.svc: i/o timeout
2023-09-16T10:18:36.202Z [ERROR] Unexpected error looking for preexisting bootstrap Secret: context deadline exceeded

2

Hi @prashantnitt07,

Whenever you are reporting issues related to Consul on Kubernetes, it will be helpful if you post the Helm Values file, the Helm Chart version in use, the Kubernetes version and any additional configuration in place (e.g.: Custom CNI etc.).

From the error, it looks like there are DNS lookup issues in your cluster, which is causing the consul-server-acl-init to fail. I would recommend you try to figure out why the DNS resolution is failing.

3

Thanks for support , issues has resolved , all pods are running on eks.

I fallow and got solution for below link

Deploy Consul on Kubernetes | Consul | HashiCorp Developer

4

and additionally create sc and pv for consul server 0,1 and 2