Support Nomad Federation over Consul Mesh Gateways
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
*This is still being thought about and should not be considered an intent-to-ship at this time.*
Now that hashicorp/consul#6356 is fixed, once [the next release of Consul](https://github.com/hashicorp/consul/blob/3a9509e84d4b47a0288044c7652add5c6d5ba3fc/CHANGELOG.md) is out Consul will support WAN federation over [Connect Mesh Gateways.](https://www.consul.io/docs/connect/mesh_gateway.html)
Nomad should be able to use Mesh Gateways for its own federation.
This may require changes to Nomad's serf/memberlist usage, but since Nomad only minimally uses serf for raft membership this should hopefully be non-disruptive (and potentially allows us to remove the dedicated serf port).
Contributor guide
No contributing guide indexed for this repository
Research direction
No Nomad files, tests, or entry points are named. Start by reviewing Nomad's Serf/memberlist usage and the Consul Mesh Gateway federation change referenced in the issue; done means defining and implementing federation over Mesh Gateways without disrupting Raft membership.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100