[M4.1] WireGuard mesh

Open
  • Is something wrong?
#224 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
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
infrastructure, networking

Research direction

Start by locating the agent and control-plane entry points for task M4.1 and review the implementation of dependency M1.2. Identify how nodes are configured and how the project provisions VMs across providers. Done means three VMs across two providers communicate over a WireGuard mesh, including one VM behind NAT.

Written by the indexing model from the issue text.

Description

blocked priority:P1 task track:agent track:control-plane
Task id

M4.1

Track

A: agent, C: control plane

Scope
  • Key generation on node, IP allocation per org CIDR, ConfigurePeers, NAT traversal via persistent keepalive and endpoint discovery.
Acceptance criteria

Three VMs in two providers communicate over the mesh; one behind NAT.

Depends on

M1.2

Blocked by

VMs in two providers.

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.