Binding service on a specific subnet
Open
Nobody has claimed this yet.
enhancement
Priority: Medium
size/S
v2
V3
- Dominant language
- Java
- Stars
- 92
- Forks
- 81
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 46
Description
This issue is based on #4408
For each service should be possible to configure network for binding a port. As default services binds on 0.0.0.0 (all network interfaces). It is valid for v3, but not for v2. All except the Gateway are binding always on all interfaces, see -Dserver.address=0.0.0.0 \ in all start.sh scripts.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with issue #4408 and the start.sh scripts containing -Dserver.address=0.0.0.0; trace how each service receives its binding configuration and compare it with the Gateway behavior. Done means each service can select the network interface for its port while retaining the current all-interface default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, shell
- Domain
- api, backend, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100