Skip to content

fix(containerlab): give ns30/ns40 two attachments, not one shared - #313

Open
privateip wants to merge 1 commit into
fix/vrf-shared-per-vpc-2-cnibgpfrom
fix/vrf-shared-per-vpc-3-containerlab
Open

fix(containerlab): give ns30/ns40 two attachments, not one shared#313
privateip wants to merge 1 commit into
fix/vrf-shared-per-vpc-2-cnibgpfrom
fix/vrf-shared-per-vpc-3-containerlab

Conversation

@privateip

@privateip privateip commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

Summary

ns30/ns40 modeled "two pods, one VPC, one node" as one NAD scaled to two replicas, sharing a single attachment identifier — the setup that triggered the VRF collision fixed earlier in this stack. Each now gets its own NAD and Deployment with a distinct attachment under the same VPC, matching how every other tenant fixture models one attachment as one pod.

Test plan

  • task verify passes end-to-end on a live containerlab lab, including ns30/ns40's two-attachment same-node pings
  • ns30's two pods are confirmed sharing one kernel VRF across distinct attachments

Stack (merge bottom to top):

🤖 Generated with Claude Code

@privateip
privateip requested a review from a team as a code owner August 8, 2026 17:44
@privateip
privateip requested review from drewr and removed request for a team August 8, 2026 17:44
@privateip
privateip force-pushed the fix/vrf-shared-per-vpc-3-containerlab branch from 86e74e4 to 1be86f5 Compare August 8, 2026 19:05
@privateip
privateip requested review from 0xmc, scotwells and slindseysr and removed request for drewr August 8, 2026 19:13
Rebased onto the updated fix/vrf-shared-per-vpc-2-cnibgp (which
picked up my own rebase-and-reconcile of that branch after
fix/vrf-shared-per-vpc-1-core moved out from under it) after that
branch's history moved out from under this one -- same ripple as
#306 -> #307 -> #311 -> #312 -> #313.

No conflicts: this PR only touches containerlab docs/scripts/
manifests, none of which overlapped with the Go source changes further
up the stack. Applied cleanly.

Verification: task lint, task build (all 8 binaries) pass on the
rebased tree. No Go source changed in this PR, so task test:unit is
unaffected. tests/e2e and the containerlab lab itself not run in this
sandbox (no Kind cluster / root), same caveat as every PR in this
stack.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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