Add ability to specify server RPC address to bind to
- Dominant language
- Go
- Stars
- 30.1k
- Forks
- 4.6k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 39
Description
#### Feature Description
Currently, it is possible to adjust the address binding of dns, http, https, grpc, grpc TLS, serf-lan and serf-wan. But as far as I can see it is not possible to adjust the server RPC address binding (port 8300), it always uses `bind_addr` which has other implications as well.
#### Use Case(s)
In a temporary environment with multiple consul servers on one node I need `bind_addr` to be 0.0.0.0, but limit server RPC to a specific address.
Contributor guide
Research direction
Start by tracing how Consul configures the server RPC listener on port 8300 and how the existing bind_addr settings reach the other listed protocols. Determine where a separate RPC address can be represented and configured. Done means server RPC can bind to a specified address independently while the temporary multi-server use case works without changing the other bindings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100