Why does a Second Network Interface get its own VPC in GCP

Why does a second network interface require a separate VPC (subnet in a separate VPC) to attach to?

The reason has to do partly with the way routes are inherited by network interfaces.

NICs automatically inherit default routes from the global routing table defined at the VPC Level.

The question then arises - if you add a second NIC, what is the advantage of it inheriting exactly the same routes?

Since the idea of a second NIC is typically to provide additional (Secondary) network routing, it makes sense to attach it to a second VPC that is different from the first.



Need an experienced AWS/GCP/Azure Professional to help out with your Public Cloud Strategy? Set up a time with Anuj Varma.

anuj

I am passionate about getting cloud solutions right the first time. I help customers transition to the public cloud with the appropriate security controls and guardrails. GCP, AWS and Azure Security Specialist. <a href="https://calendly.com/anujvarma/google-cloud-architect-initial-consultation">Initial Consultation</a>

Leave a reply

Your email address will not be published. Required fields are marked *