Node names, labels and namespaces
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.7k
- Forks
- 676
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
Node is the only resource not created by users. A node has both a name (hostname) and labels (docker engine labels), but we don't want to put them in Spec.Meta since we are not supposed to touch Specs with non-user data.
Also, while other objects have name uniqueness guarantees, we cannot guarantee that for nodes (it's perfectly fine for two nodes to have the same hostname, I guess).
Another weirdness: nodes don't belong to namespaces.
Should we remove Meta altogether from NodeSpec?
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 by reviewing NodeSpec and Spec.Meta, then trace how node names, Docker Engine labels, uniqueness, and namespaces are represented. The issue needs a design decision before implementation; done means the chosen node metadata and identity semantics are documented and consistently represented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100