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
Add Cluster/Client Advertise to cluster config #32
Comments
pires
added a commit
that referenced
this issue
Dec 9, 2018
Fixes #32 Signed-off-by: Paulo Pires <pjpires@gmail.com>
wallyqs
pushed a commit
to wallyqs/nats-operator
that referenced
this issue
Feb 22, 2019
Fixes nats-io#32 Signed-off-by: Paulo Pires <pjpires@gmail.com>
wallyqs
pushed a commit
to wallyqs/nats-operator
that referenced
this issue
Feb 23, 2019
Fixes nats-io#32 Signed-off-by: Paulo Pires <pjpires@gmail.com>
wallyqs
pushed a commit
that referenced
this issue
Feb 26, 2019
Fixes #32 Signed-off-by: Paulo Pires <pjpires@gmail.com>
wallyqs
pushed a commit
that referenced
this issue
Feb 26, 2019
Fixes #32 Signed-off-by: Paulo Pires <pjpires@gmail.com>
wallyqs
pushed a commit
that referenced
this issue
Feb 26, 2019
Fixes #32 Signed-off-by: Paulo Pires <pjpires@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently when TLS is setup for clients and routes, the NATS clients receive routes as IPs via auto discovery so hostname verification would fail when reconnecting to one of these IPs. Setting instead the pods to advertise the A record that they get in the cluster would allow clients to be able to failover to an available node right away.
https://github.com/nats-io/gnatsd/blob/163ba3f6a7521300a4f578eb90b9ff5d40d658c4/main.go#L24
https://github.com/nats-io/gnatsd/blob/163ba3f6a7521300a4f578eb90b9ff5d40d658c4/main.go#L51
The text was updated successfully, but these errors were encountered: