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.