Consul: 0.7.2
You may have crashed your cluster so that all Consul servers have been offline at some point. You may be running on Kubernetes. The default 96 hours didn't pass, so there was no reaping of Consul servers. Restarting it all doesn't work. You've read this issue five times over and nothing works. On top of it all, which makes it harder, you're running a StatefulSet on Kubernetes, so you need to do kubectl delete pods/consul-1
to make the container arguments (kubectl replace consul/consul.yml
) bite. On top of this, if you kubectl exec -it consul-1
and then kill -9 5
, Kubernetes goes into a crash loop with exponential backoff, eating into your time.
Sounds like a Friday pleasure, right?
The tools you have at your disposal are:
-bootstrap
kubectl replace consul/consul.yml