Allow disabling binding to http/rpc ports on clients
Open
theme/client
type/enhancement
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
Since Nomad 0.8, Clients no longer need to bind to http/rpc ports for allocation logs/fs requests. Nomad should allow starting client agents with -1 as the http/rpc ports. Will need changes to how ephemeral disk migration works to support this.
More discussion context in #4482
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the discussion in #4482, then trace client HTTP/RPC port binding and the ephemeral disk migration behavior. The change is complete when a client agent can start with -1 for both ports while allocation logs/filesystem requests and ephemeral disk migration continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100