Skip to content
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

website: fix typo #936

Merged
merged 1 commit into from
May 14, 2015
Merged

website: fix typo #936

merged 1 commit into from
May 14, 2015

Conversation

ceh
Copy link
Contributor

@ceh ceh commented May 14, 2015

Clarify that the user is assured that Consul will listen to a
specific address when specifying a bind address, rather than
providing some kind of insurance policy.

/cc @ryanbreen

Clarify that the user is assured that Consul will listen to a
specific address when specifying a `bind` address, rather than
providing some kind of insurance policy.
@ryanbreen
Copy link
Contributor

Great catch!

ryanbreen added a commit that referenced this pull request May 14, 2015
@ryanbreen ryanbreen merged commit c690770 into hashicorp:master May 14, 2015
@ceh ceh deleted the intro-getting-started-join-typo branch May 14, 2015 15:47
duckhan pushed a commit to duckhan/consul that referenced this pull request Oct 24, 2021
Don't set `-disable-host-node-id=false` on Consul Clients because it causes Clients to
not be able to join the cluster on certain hypervisor or Kind setups. This flag was
added in 0.30.0 to stop Consul logging an error when a Client pod was force deleted
but this error does not affect the pod restarting so removing the flag will have
no real effect.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants