-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Several items from Cloud Foundry usage of Consul #2343
Comments
Hey @slackpad any update on any of these issues, or ideas on how we can help? |
Keyring API will be done under #2502. |
Leave was done under #2516. |
An automatic check for this was added in 0.7 if you use bootstrap expect. The servers query each other and make sure the other servers aren't part of an existing cluster before bootstrapping, so it's always possible to leave bootstrap-expect set. |
https://www.consul.io/docs/guides/autopilot.html#server-health-checking |
https://www.consul.io/docs/guides/autopilot.html#stable-server-introduction |
Hey @slackpad, thanks for meeting with some of us from the Pivotal Cloud Foundry team, here's some of the points we talked about.
leave
command, instead of only RPC interface.consul
CLI supporting commands to remote servers and supporting flags for TLS things -- needs to support just giving it an IP and maybe ignoring domain name verification (chicken-egg problem).Some of the items above are maybe a bit roughly worded, we can work on refining them.
Also, please let us know how we can help on these via PRs.
Thanks!
The text was updated successfully, but these errors were encountered: