Define schema for mapping service resources into DNS
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.7k
- Forks
- 676
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
While there has been discussion in https://github.com/docker/docker/pull/24973 and
https://github.com/docker/swarmkit/issues/192, the adoption of a clear schema for mapping service resources into the DNS space is unclear.
The following presents a schema for mapping cluster-level FQDNs from various components:
| Resource | Component | Structure | Examples |
|---|---|---|---|
| Cluster | <cluster> |
<cluster> |
local, cluster0 |
| Namespace | <namespace> |
<namespace>.<cluster> |
production.cluster0, development.local, system |
| Node | <node> |
<node>.<cluster> |
node0.local |
| Job | <job> |
<job>.<namespace>.<cluster> |
job0.production.cluster0 |
| Slot | <slot> |
<slot id>.<job>.<namespace>.<cluster> |
1.job0.production.cluster0 |
| Task | <task> |
<task id>.<slot id>.<job>.<namespace>.<cluster> |
abcdef.1.job0.production.cluster0 |
@mavenugo @mrjana @aluzzardi
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 reading the linked Docker pull request and SwarmKit issue, then review this issue's discussion and proposed resource hierarchy. There are no files, tests, or entry points named in the payload. Done means reaching agreement on a clear DNS schema for the listed cluster, namespace, node, job, slot, and task resources.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 22/100