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
At present, if there is a cluster of hosts and the natscli connects but the TLS cert fails to verify, it appears that it will use the pre-TLS INFO line to look at alternative host IPs reported and try them in turn, until one connects.
But that happens without diagnostic feedback. Which is great for self-healing resiliency, but not for cluster administrators trying to carefully watch the rollout of a change.
Use case
If doing upgrades and trying to see TLS change impact, it's good to know which server is actually being talked to. Having --debug report connection attempts would make it clearer when silent reconnections are happening. Having a --no-reconnect might help too.
Contribution
Sure
The text was updated successfully, but these errors were encountered:
Proposed change
At present, if there is a cluster of hosts and the natscli connects but the TLS cert fails to verify, it appears that it will use the pre-TLS INFO line to look at alternative host IPs reported and try them in turn, until one connects.
But that happens without diagnostic feedback. Which is great for self-healing resiliency, but not for cluster administrators trying to carefully watch the rollout of a change.
Use case
If doing upgrades and trying to see TLS change impact, it's good to know which server is actually being talked to. Having
--debug
report connection attempts would make it clearer when silent reconnections are happening. Having a--no-reconnect
might help too.Contribution
Sure
The text was updated successfully, but these errors were encountered: