GKE networking (VPC-native) in GCP - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does VPC-native mode mean in GKE networking?

VPC-native mode means GKE uses alias IPs to assign IP addresses to pods directly from a Virtual Private Cloud (VPC) subnet, allowing better IP management and network isolation.

intermediate

Why is VPC-native mode preferred over routes-based networking in GKE?

VPC-native mode scales better, avoids IP conflicts, and simplifies network management by using alias IPs instead of creating many routes for pods.

beginner

What is an alias IP range in the context of GKE VPC-native clusters?

An alias IP range is a block of IP addresses within a VPC subnet reserved for pods and services, enabling pods to have their own IPs without using node IPs.

intermediate

How does VPC-native mode improve pod-to-pod communication across nodes?

Because pods have IPs from the VPC subnet, they can communicate directly without NAT or extra routing, making communication faster and simpler.

intermediate

What must you configure before creating a VPC-native GKE cluster?

You must create a VPC subnet with secondary IP ranges reserved for pods and services to use as alias IP ranges.

What is the main benefit of using VPC-native mode in GKE?

A Pods get IP addresses from the VPC subnet directly

B Pods share the node's IP address

C Pods use external IPs for communication

D Pods do not require IP addresses

In VPC-native mode, pods receive IP addresses from the VPC subnet using alias IPs, enabling direct communication.

What must be set up in the VPC before creating a VPC-native GKE cluster?

A Firewall rules for external access

B Secondary IP ranges for pods and services

C VPN connection to on-premises

D Static routes for pods

Secondary IP ranges are required to allocate IPs to pods and services in VPC-native clusters.

How does VPC-native mode affect network scalability in GKE?

A Reduces scalability due to IP conflicts

B Has no effect on scalability

C Improves scalability by avoiding route explosion

D Requires manual IP management

VPC-native mode uses alias IPs, which avoids creating many routes and improves scalability.

In VPC-native GKE clusters, how do pods communicate across nodes?

A Directly using their VPC IP addresses

B Through node IP NAT translation

C Using external IP addresses

D Via a load balancer

Pods communicate directly using their own IPs from the VPC subnet without NAT.

Which of the following is NOT true about VPC-native GKE clusters?

A Pods have unique IPs from the VPC subnet

B Requires secondary IP ranges in the subnet

C Supports better network isolation

D Pods share the node's IP address

In VPC-native mode, pods do NOT share the node's IP; they have their own IPs.

Explain how VPC-native mode changes pod IP addressing in GKE.

Think about how pods get their IPs compared to older methods.

Describe the steps to prepare a VPC for a VPC-native GKE cluster.

Focus on IP range setup before cluster creation.

Practice

1. What does enabling VPC-native mode in GKE do for your cluster's pods?

easy

A. Uses external IP addresses for pods by default

B. Assigns IP addresses to pods from the VPC network's secondary IP ranges

C. Disables network isolation between pods

D. Requires manual IP address assignment for each pod

Solution

1. Step 1: Understand VPC-native mode purpose

   VPC-native mode allows pods to get IPs from the VPC network's secondary IP ranges instead of using NAT or external IPs.

2. Step 2: Identify pod IP assignment behavior

   Pods receive IP addresses from the VPC's secondary IP ranges, enabling better network control and integration.

3. Final Answer:

   Assigns IP addresses to pods from the VPC network's secondary IP ranges -> Option B

4. Quick Check:

   VPC-native pods get IPs from VPC secondary ranges [OK]

Hint: Remember pods get IPs from VPC secondary ranges in VPC-native mode [OK]

Common Mistakes:

• Thinking pods use external IPs by default
• Assuming manual IP assignment is needed
• Believing network isolation is disabled

2. Which gcloud command flag enables VPC-native mode when creating a GKE cluster?

easy

A. --enable-network-alias

B. --enable-vpc-native

C. --enable-ip-alias

D. --use-secondary-ip

Solution

1. Step 1: Recall the flag for VPC-native mode

   The correct flag to enable VPC-native mode is --enable-ip-alias when creating the cluster.

2. Step 2: Verify other options

   Other options like --enable-vpc-native or --use-secondary-ip are incorrect or do not exist.

3. Final Answer:

   --enable-ip-alias -> Option C

4. Quick Check:

   Enable VPC-native with --enable-ip-alias [OK]

Hint: Use --enable-ip-alias to activate VPC-native mode [OK]

Common Mistakes:

• Using non-existent flags like --enable-vpc-native
• Confusing flag names with similar terms
• Omitting the flag entirely

3. Given this command snippet:

gcloud container clusters create my-cluster \
  --enable-ip-alias \
  --create-subnetwork name=my-subnet,range=10.0.0.0/24 \
  --cluster-secondary-range-name=pods-range \
  --services-secondary-range-name=services-range

What is the purpose of specifying --cluster-secondary-range-name?

medium

A. Defines the IP range for the cluster's nodes

B. Sets the IP range for external load balancers

C. Allocates IP range for Kubernetes services

D. Specifies the IP range for pods in the cluster

Solution

1. Step 1: Understand secondary IP ranges in VPC-native

   In VPC-native clusters, secondary IP ranges are used to assign IPs to pods and services separately.

2. Step 2: Identify the role of cluster-secondary-range-name

   The --cluster-secondary-range-name flag specifies the secondary IP range used for pods.

3. Final Answer:

   Specifies the IP range for pods in the cluster -> Option D

4. Quick Check:

   Cluster secondary range = pod IP range [OK]

Hint: Cluster secondary range is for pods, services range is for services [OK]

Common Mistakes:

• Confusing pod IP range with node IP range
• Mixing up services and pods secondary ranges
• Assuming it sets external IP ranges

4. You created a GKE cluster with --enable-ip-alias but pods cannot reach services in the same cluster. What is a likely cause?

medium

A. Secondary IP ranges for pods and services were not properly configured

B. The cluster was created without a node pool

C. The VPC network has no firewall rules allowing pod traffic

D. The cluster is missing a public IP address

Solution

1. Step 1: Check VPC-native setup requirements

   VPC-native clusters require properly configured secondary IP ranges for pods and services to communicate.

2. Step 2: Identify common misconfiguration

   If pods cannot reach services, it often means the secondary IP ranges were not set or assigned correctly.

3. Final Answer:

   Secondary IP ranges for pods and services were not properly configured -> Option A

4. Quick Check:

   Pod-service reachability needs correct secondary IP ranges [OK]

Hint: Check secondary IP ranges if pods can't reach services [OK]

Common Mistakes:

• Assuming missing node pool causes pod-service issues
• Thinking public IP is needed for internal pod communication
• Ignoring firewall rules impact on pod traffic

5. You want to create a GKE cluster with VPC-native networking that supports up to 1000 pods per node. Which configuration is necessary?

hard

A. Use --enable-ip-alias with a large enough secondary IP range for pods per node

B. Assign external IPs to pods and increase node IP range

C. Disable IP aliasing and use NAT for pod IPs

D. Create multiple clusters each with small pod IP ranges

Solution

1. Step 1: Understand pod IP allocation in VPC-native mode

   Pods get IPs from the secondary IP range assigned to the cluster. To support many pods per node, the secondary range must be large enough.

2. Step 2: Identify correct configuration for high pod density

   Using --enable-ip-alias with a sufficiently large secondary IP range allows scaling pods per node without IP conflicts.

3. Final Answer:

   Use --enable-ip-alias with a large enough secondary IP range for pods per node -> Option A

4. Quick Check:

   Large secondary IP range + --enable-ip-alias = high pod density [OK]

Hint: Large secondary IP range needed for many pods per node [OK]

Common Mistakes:

• Assigning external IPs to pods unnecessarily
• Disabling IP aliasing reduces pod IP control
• Splitting pods across clusters instead of scaling IP range