Sharing (network) namespaces in global mode
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.7k
- Forks
- 676
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
I would like to stack multiple services ontop of each other, so that I can come closer to my dream of having one process per container.
In retrospect it looks a lot like what kubernetes is actually doing.
- starting a dummy container which provides the network namespace
- starting a syslog container hooking into the dummy to provide a syslog endpoint
- starting a metrics collector hooking into the dummy
- starting the actual service in question
From where I stand this can only be accomplished in global mode, as otherwise the scheduling would be hardly constrainted and if the replica-count on both services is different the service that relies on the first one is screwed anyway.
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
No files, tests, or entry points are named. Start by tracing global-mode scheduling and network-namespace handling, then define how stacked services and differing replica counts should be represented and verified; the issue does not provide acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100