Kubernetes Engine Communication Through VPC PeeringIr al Laboratorio
there is a small typo when referring to subnets in the validation step. the subnets created are actually us-central1 and us-east1 but there you refer to them as us-west1 and us-east1, which might be confusing for someone else =)
The lab script has discrepancies to the actual lab that is very confusing (regions where clusters are deployed etc.).
very short, need to research in shell script files :|
Wish there was more explanation or exploration of the VPC peering, another Kube lab where 90% of the time is setting up and tearing down.