1. Home
  2. Training Library
  3. Google Cloud Platform
  4. Courses
  5. Implementing a GCP Virtual Private Cloud (VPC)

Non-VPC-Native GKE Clusters

Start course
Duration1h 15m


Please note: this course has been replaced with an updated version which can be found here.


This course guides you through the key steps to configure a Google Cloud Platform virtual private cloud (VPC), which allows you to connect your GCP services with one another securely.

After a brief introduction, the course begins with how to set up and configure VPCs, including VPC peering and shared VPC. You'll learn how to configure routes, set up cloud NAT (network address translation), and configure VPC-native clusters in Kubernetes, before rounding off the course by looking at VPC firewalls. The topics in this course are accompanied by demonstrations on the platform in order to show you how these concepts apply to real-world scenarios.

If you have any feedback, questions, or queries relating to this course, please feel free to contact us at support@cloudacademy.com.

Learning Objectives

  • Configure Google Cloud Platform VPC resources
  • Configure VPC peering and API access
  • Create shared VPCs
  • Configure internal static and dynamic routing, as well as NAT
  • Configure and maintain Google Kubernetes Engine clusters
  • Configure and maintain VPC firewalls

Intended Audience

This course is intended for:

  • Individuals who want to learn more about Google Cloud networking, who may also have a background in cloud networking with other public cloud providers
  • Individuals who simply want to widen their knowledge of cloud technology in general


To get the most from this course, you should already have experience in public cloud and networking as well as an understanding of GCP architecture.


Now for the next part, we're gonna go look at a GKE cluster that is not VPC native. So on the screen here, you could see this is another cluster, it's been set up and the VPC native alias IP is disabled. But on this one, you're gonna see the pod address range at the and you're also gonna notice there's no service range down here at all 'cause that's all just gonna get picked for you.

So when we go down here to the bottom, what we're gonna do is we're gonna go ahead and run that kubectl get pods and you're gonna see all the pods here and they're gonna be in that range which is great, it's just that I didn't get to choose this range, therefore it's just gonna make things a lot more random and not predictable in the sense of if you're dealing with a big network or if you're doing some, let's say, hybrid or however you're routing your network routing map is set up, this isn't gonna work as well because you can just get any IP range that it wants to give you.

So hopefully this helps break down some of the differences between native VPC and also non-native VPC. Thanks for watching. Let's move on to the next section.

About the Author

Mark has many years of experience working with Google Cloud Platform and also holds eight GCP certifications.