server: join semantics are not exposed via configuration

[macb]

Similar to how consul offers flags and config file to have a server join the cluster nomad doesn't. Was this an intended deviation?

[ryanuber]

@macb this was probably just an oversight for the servers. In Nomad the client's don't need to join the gossip pool, so only the server nodes should need these options. We should add them, though. Thanks!

[ketzacoatl]

I am really appreciative for the flexibility and simplicity inherent in Consul's leader election, and the lack of the same semantics in Nomad makes deploying Nomad leaders to AWS auto-scaling groups much more difficult than Consul. (I would welcome any suggestions - in case I am missing something obvious).

To be more clear: the current setup with Consul makes it possible to easily give Consul an arbitrary list of IPs, and set it up to continually retry/reload/restart until Consul succeeds to elect a leader.

There is a bit of a discussion on these topic on the list: https://groups.google.com/d/msg/nomad-tool/PXH0rQK_7sM/zQMP3mRIDwAJ

[adrianlop]

+1

[dadgar]

#527 addresses this!

[ketzacoatl]

\o/

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.