Migrating to NCC in parallel with adding Partner Interconnects
Got a oddly specific situation right now, just was curious for experience/insights.
We need to migrate to NCC later this year due to approaching hard quotas around peering. Plot twist: I need to add some 10 Gbps partner interconnects in the next 1-2 months. Reason is political pressure as there's "concerns" that VPNs can't provide adequate bandwidth for future growth.
The existing topology is hub/spoke, with multiple VPNs in the hub. The hub VPC is in a separate project than all the spokes (which we've realized was really a mistake by our architecture group at the time). Spokes connect to hub via peering or internal VPN.
We definitely want the NCC hub to be in the same project as all spokes, when possible. Of these options, which makes the most sense?
Create an NCC hub, bring the interconnects on a hybrid spoke, immediately migrate the existing spokes and hub to NCC as required.
Create a new, separate VPC network for the interconnects, use traditional peering to required spokes that need the interconnect. Immediately after, create an NCC hub and migrate everything existing.
Ignore NCC for now. Add the Interconnects to the existing hub. Start a fresh NCC hub and migrate everything later. This would eventually require moving the interconnects to a different network and project, which I'm concerned might get messy.