[M4.2] Internal DNS and service discovery

Open
#225 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
networking

Research direction

Start by locating the implementation and acceptance tests for M4.1, since this task depends on it; the issue names no files or test commands. Trace how nodes connect over the WireGuard interface, then identify where embedded DNS and service discovery belong. Done means an app on node A can reach a database on node B using the specified internal name.

Written by the indexing model from the issue text.

Description

priority:P2 task track:agent
Task id

M4.2

Track

A: agent

Scope
  • Embedded DNS on the WireGuard interface for <app>.<env>.<project>.internal.
Acceptance criteria

App on node A reaches database on node B by name.

Depends on

M4.1

Dominant language
TypeScript
Stars
2
Forks
1
Avg merge
7h 17m
Merged PRs (30d)
197

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from shipkeepdev/shipkeep

All issues in shipkeepdev/shipkeep

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.