Consul_Kubernetes_Installation Issue

[Yukeshraja]

Hi Team,

I have a Kubernetes 3Node cluster with rook as a storage class (Default). I tried to install the consul in kubernetes facing below issues.

I added rook as storage class in the volume.yaml but still the issue persists.

Running a fresh installation using bootstrapACLs is running into a deadlock
The consul-server-acl-init job is responsible for bootstrapping ACLs on the server (generating the bootstrap token & generating the server token) and is a job with a post-install hook.
The consul client pod has an initContainer "client-acl-init" which is stuck waiting for that bootstrap token secret and so, pod installation won't finish until the bootstrap token exists.
So, the consul-server-acl-init job will only kick off when installation is finished but installation can't finish until the consul-server-acl-init job runs.

Thanks in advance.

[lkysow]

Hi @Yukeshraja,
The consul-server-acl-init Job needs the Consul servers to elect a leader before it can succeed. What does the output of kubectl get pod | grep consul say? I would look at the logs for the Consul servers and see if they're running and have elected a leader successfully. Also can you show us the logs for the server-acl-init Job?

Finally, the latest version of this chart (v0.11.0) has some bugfixes so I'd recommend trying with that.

[Yukeshraja]

[Yukeshraja]

Hi,

Facing below issue.

[adilyse]

Related: #10