Subnet IP ranges can't overlap across peered VPC networks No subnet IP range can exactly match, contain, or fit within another subnet IP range in a peered VPC network. At the time of peering, Google Cloud checks if subnets with overlapping IP ranges exist; if they do, then the peering fails. For already peered networks, if you perform an action that results in the creation of a new subnet route, Google Cloud requires the new subnet route to have a unique destination IP address range.
Great video Bro, Your videos have always helped me to understand GCP concepts!
Thanks, Bro great video!!!
Thanks bro🎉
Hi Tech Trapture, can u please help me in setting up cron job for log archival and deletion using terraform in gcp.
Sure , I will help.can you please Share me your email id ?
could there be an IP conflict between the 2 networks? what if there is a vm in vpc-a and another vm with same IP in vpc-b?
Subnet IP ranges can't overlap across peered VPC networks
No subnet IP range can exactly match, contain, or fit within another subnet IP range in a peered VPC network. At the time of peering, Google Cloud checks if subnets with overlapping IP ranges exist; if they do, then the peering fails. For already peered networks, if you perform an action that results in the creation of a new subnet route, Google Cloud requires the new subnet route to have a unique destination IP address range.
Can not connect to ssh. What should I do?
Create firewall to allow traffic on port 22.
@@techtrapture already created sir. It doesn't work
What is the error? Does VM have both public & private IP or Private IP only?