We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When using the latest 1.0.0 helm charts, server names use POD_NAME, however, if we try to connect two clusters, POD_NAME is not enough.
[7] 2023/06/12 21:22:47.289101 [INF] 10.42.3.0:4148 - gid:2059 - Processing inbound gateway connection [7] 2023/06/12 21:22:47.326922 [ERR] 10.42.3.0:4148 - gid:2059 - Remote server has a duplicate name: "nats-2" [7] 2023/06/12 21:22:47.326934 [INF] 10.42.3.0:4148 - gid:2059 - Gateway connection closed: Duplicate Server Name
In the previous helm charts, there was something called server_name_prefix that could be applied to each separate deployment
The text was updated successfully, but these errors were encountered:
config.serverNamePrefix should be available now in 1.0.0-beta.6
config.serverNamePrefix
Sorry, something went wrong.
OMG!! this is SO good! thanks!
No branches or pull requests
When using the latest 1.0.0 helm charts, server names use POD_NAME, however, if we try to connect two clusters, POD_NAME is not enough.
In the previous helm charts, there was something called server_name_prefix that could be applied to each separate deployment
The text was updated successfully, but these errors were encountered: