You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.
If you increase and then decrease the cluster size... you lose the cluster leader and are then unable to recover.
I mentioned this here and submitted a PR, when this was still in the incubator, but never came to a final solution.
Thanks for raising this @ajohnstone. This is actually part of a bigger issue with consul when using the bootstrap-expect parameter. It seems that the solution is to get autopilot working in 0.8.0. Here's the upstream issue. hashicorp/consul#993
Thanks for the quick response, would be good to add PodDisruptionBudget and this feature to be enabled by default if >=0.8.0. When searching before I got lost in very old tickets 👍
If you increase and then decrease the cluster size... you lose the cluster leader and are then unable to recover.
I mentioned this here and submitted a PR, when this was still in the incubator, but never came to a final solution.
Issue: kelseyhightower/consul-on-kubernetes#6
PR: kelseyhightower/consul-on-kubernetes#7
Tested again on consul:0.2.0
@lachie83 Any further ideas on this?
The following is a good suggestion, but does not fix the underlying problem.
The text was updated successfully, but these errors were encountered: