Skip to content

chore: clarify v4 ns constraint for ext peering #273

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Frostman merged 1 commit into from
Mar 5, 2026
Merged

chore: clarify v4 ns constraint for ext peering #273

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/user-guide/external.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -176,7 +176,8 @@ spec:
### External VPC Peering

To allow a specific VPC to have access to prefixes reachable via an Edge Device, bind the VPC to the corresponding
`External` by creating an `External Peering` object.
`External` by creating an `External Peering` object. Both the VPC and the external must belong to the same
`IPv4Namespace`; peering of VPCs and externals from different IPv4 namespaces is not supported.

!!! note
External VPC Peering via this Fabric object is only supported for BGP-speaking externals or
Expand Down