Skip to content

Support multiple external IPs in blueprint zone type - #11236

Open
bnaecker wants to merge 1 commit into
mainfrom
ben/multiple-eips-in-blueprint-zone-types
Open

Support multiple external IPs in blueprint zone type#11236
bnaecker wants to merge 1 commit into
mainfrom
ben/multiple-eips-in-blueprint-zone-types

Conversation

@bnaecker

@bnaecker bnaecker commented Sep 3, 2026

Copy link
Copy Markdown
Collaborator
  • Add support for multiple EIPs to the blueprint zone types for Nexus, External DNS, and Boundary NTP zones.
  • Add some newtypes and wrappers to support lists of these or up to 2 of them for the SNAT case of Boundary NTP.
  • Add a test that the full blueprint with multiple addresses round-trips through the database.
  • Planner still emits exactly one address in all these cases, this is only the structural change to support multiple addresses.
  • Update lockstep OpenAPI docs

- Add support for multiple EIPs to the blueprint zone types for Nexus,
  External DNS, and Boundary NTP zones.
- Add some newtypes and wrappers to support lists of these or up to 2 of
  them for the SNAT case of Boundary NTP.
- Add a test that the full blueprint with multiple addresses round-trips
  through the database.
- Planner still emits exactly one address in all these cases, this is
  only the structural change to support multiple addresses.
- Update lockstep OpenAPI docs
@bnaecker
bnaecker force-pushed the ben/multiple-eips-in-blueprint-zone-types branch from 536f509 to fca831a Compare September 4, 2026 16:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant