Skip to content

wip tagged nat_apply - #333

Draft
nicolaskagami wants to merge 8 commits into
nsk/nat-3-natmapfrom
nsk/service-nat-entries
Draft

wip tagged nat_apply#333
nicolaskagami wants to merge 8 commits into
nsk/nat-3-natmapfrom
nsk/service-nat-entries

Conversation

@nicolaskagami

Copy link
Copy Markdown

No description provided.

@nicolaskagami
nicolaskagami force-pushed the nsk/service-nat-entries branch from 7fa4258 to 267c875 Compare August 6, 2026 14:50
@nicolaskagami
nicolaskagami changed the base branch from main to nsk/nat-3-natmap August 6, 2026 14:51
@nicolaskagami
nicolaskagami force-pushed the nsk/service-nat-entries branch 2 times, most recently from ce210d2 to b19eeae Compare August 7, 2026 12:48
PUT /nat/tagged/{tag}/ipv4 and /ipv6 take the complete desired set of
NAT entries for a tag, diff it against current state under a single
acquisition of the NAT lock, and converge. Entries created this way
carry the tag; entries absent from a later apply are removed, and an
empty apply removes them all. Conflicts with entries not carrying the
tag and dataplane failures are reported per entry rather than failing
the request. GET on the same paths lists the entries carrying a tag.
Cover convergence (add/remove/retarget/idempotent re-apply), isolation
between tags and from untagged entries, per-entry conflict reporting,
wholesale rejection of invalid requests, empty-apply removal, and
tagged list pagination.
Adds nat apply-ipv4/apply-ipv6, which read a JSON array of NAT entries
and PUT it as the complete set for a tag, and a -t/--tag filter on nat
list.
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