GKE networking (VPC-native) in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable VPC-native mode when creating a GKE cluster.

GCP

gcloud container clusters create my-cluster --enable-ip-alias=[1]

Drag options to blanks, or click blank then click option'

Afalse

Btrue

Cauto

Dnone

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'false' disables VPC-native mode.

Using 'auto' or 'none' are invalid values for this flag.

To enable VPC-native mode, you must set --enable-ip-alias to true.

2fill in blank

medium

Complete the code to specify the secondary range for pods in a VPC-native GKE cluster.

GCP

gcloud container clusters create my-cluster --enable-ip-alias --cluster-secondary-range-name=[1]

Drag options to blanks, or click blank then click option'

Adefault

Bservices-range

Cprimary-range

Dpods-range

Attempts:

3 left

💡 Hint

Common Mistakes

Using the primary subnet range instead of a secondary range.

Confusing service range with pod range.

The --cluster-secondary-range-name flag specifies the secondary subnet range used for pods. It is commonly named like pods-range.

3fill in blank

hard

Fix the error in the command to create a VPC-native GKE cluster with correct service secondary range.

GCP

gcloud container clusters create my-cluster --enable-ip-alias --services-secondary-range-name=[1]

Drag options to blanks, or click blank then click option'

Aservices-range

Bprimary-range

Cpods-range

Ddefault

Attempts:

3 left

💡 Hint

Common Mistakes

Using the pod range for services causes IP conflicts.

Using the primary range instead of a secondary range.

The --services-secondary-range-name flag must point to the secondary subnet range reserved for services, usually named services-range.

4fill in blank

hard

Fill both blanks to create a VPC-native GKE cluster with correct secondary ranges for pods and services.

GCP

gcloud container clusters create my-cluster --enable-ip-alias --cluster-secondary-range-name=[1] --services-secondary-range-name=[2]

Drag options to blanks, or click blank then click option'

Apods-range

Bdefault

Cservices-range

Dprimary-range

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up pod and service ranges.

Using the primary range instead of secondary ranges.

The --cluster-secondary-range-name should be the pods subnet range, and --services-secondary-range-name should be the services subnet range.

5fill in blank

hard

Fill all three blanks to create a VPC-native GKE cluster with custom network, subnetwork, and enable IP aliasing.

GCP

gcloud container clusters create my-cluster --network=[1] --subnetwork=[2] --enable-ip-alias=[3]

Drag options to blanks, or click blank then click option'

Acustom-network

Bcustom-subnet

Ctrue

Ddefault-network

Attempts:

3 left

💡 Hint

Common Mistakes

Using default network names when custom ones are required.

Forgetting to enable IP aliasing.

Specify your custom VPC network and subnetwork names, and enable IP aliasing by setting --enable-ip-alias to true.

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