oxidecomputer / oxidecomputer/omicron
Tracking issue for more flexible external IP addressing for Omicron services
Open
@bnaecker is already working on this.
Since Jun 11, 2026.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Today, all Omicron zones that have an external IP address are assumed to have exactly one of them. For example, this is the one IP address that Nexus listens on. This isn't flexible enough to support things like dual IPv4 and IPv6 deployments of the same service. Note that it's also not enough to have one IP of each version (even an optional one), since it's plausible that operators want to make services available on multiple disjoint networks.
There's a lot of work needed to make this happen, tracked by individual issues below.
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.
Assessment
This issue has not been assessed yet.