Skip to content

Tracking issue for more flexible external IP addressing for Omicron services #9313

Description

@bnaecker

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions