Priority
Low
Use case / problem
Cloud-parity expectation: customers — especially hybrid setups linking an on-prem DC to the AI factory over MPLS — want to bring their own IP space, which may overlap between tenants (e.g. two tenants both using 10.0.0.0/24). NICo's IPAM currently blocks overlapping IP within a site.
Raised by
Reliance (multi-tenant AI factory, hybrid/MPLS).
Current state / workaround
- NICo enforces non-overlapping IP today (guards in VPC peering / allocation); noted as unlikely to be lifted soon.
- Workaround: handle overlapping ranges outside NICo via NAT (firewall / edge / MPLS NAT).
- Distinct from BYOIP: announcing your own (non-overlapping) prefix via host→DPU BGP is already supported (BGP-Peering page); this request is specifically about overlapping address space.
- Technically, separate VRFs/L3 VNIs can carry overlapping prefixes as long as those VPCs never interconnect, but NICo currently guards against overlap.
Ask
Capture the request and, near-term, document the limitation + NAT workaround.
Priority
Low
Use case / problem
Cloud-parity expectation: customers — especially hybrid setups linking an on-prem DC to the AI factory over MPLS — want to bring their own IP space, which may overlap between tenants (e.g. two tenants both using 10.0.0.0/24). NICo's IPAM currently blocks overlapping IP within a site.
Raised by
Reliance (multi-tenant AI factory, hybrid/MPLS).
Current state / workaround
Ask
Capture the request and, near-term, document the limitation + NAT workaround.