GKE cluster creation (Autopilot vs Standard) in GCP - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a GKE cluster in Autopilot mode.

GCP

gcloud container clusters create-auto my-cluster --region [1]

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

Aasia-east1

Bus-central1

Ceurope-west1

Dsouthamerica-east1

Attempts:

3 left

💡 Hint

Common Mistakes

Using a zone instead of a region for Autopilot clusters.

Choosing a region not supported by Autopilot.

The --region flag specifies the region for the Autopilot cluster. Here, europe-west1 is used as an example.

2fill in blank

medium

Complete the code to create a Standard GKE cluster with 3 nodes.

GCP

gcloud container clusters create my-standard-cluster --num-nodes=[1] --zone us-central1-a

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

A1

B0

C5

D3

Attempts:

3 left

💡 Hint

Common Mistakes

Setting number of nodes to zero, which is invalid.

Confusing node count with number of zones.

The --num-nodes flag sets the number of nodes in the Standard cluster. Here, 3 nodes are specified.

3fill in blank

hard

Fix the error in the command to create an Autopilot cluster by selecting the correct flag.

GCP

gcloud container clusters create my-autopilot-cluster [1] us-central1

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

A--region

B--zone

C--num-nodes

D--machine-type

Attempts:

3 left

💡 Hint

Common Mistakes

Using --zone instead of --region for Autopilot.

Adding node count flags which are not needed for Autopilot.

Autopilot clusters require the --region flag, not --zone.

4fill in blank

hard

Fill both blanks to create a Standard GKE cluster with a specific machine type and node count.

GCP

gcloud container clusters create my-standard-cluster --machine-type=[1] --num-nodes=[2] --zone us-east1-b

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

Ae2-medium

Bn1-standard-1

C3

D5

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing machine type and node count values.

Using unsupported machine types.

The --machine-type flag sets the VM type for nodes, here n1-standard-1. The --num-nodes flag sets the number of nodes, here 3.

5fill in blank

hard

Fill all three blanks to create an Autopilot cluster with a specific region and enable IP aliasing.

GCP

gcloud container clusters create-auto my-autopilot-cluster --region=[1] --enable-ip-alias=[2] --project=[3]

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

Aus-west1

Btrue

Cmy-gcp-project

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using false for IP aliasing which disables it.

Omitting the project flag or using an invalid project ID.

The --region flag sets the cluster region (us-west1). --enable-ip-alias enables IP aliasing (true). --project specifies the GCP project ID (my-gcp-project).

Practice

1. What is the main difference between a GKE Autopilot cluster and a Standard cluster?

easy

A. Autopilot manages the infrastructure automatically, while Standard requires manual node management.

B. Standard clusters automatically scale nodes, Autopilot does not.

C. Autopilot clusters only support Windows nodes, Standard supports Linux nodes.

D. Standard clusters are serverless, Autopilot clusters require manual server setup.

Solution

1. Step 1: Understand Autopilot cluster management

   Autopilot clusters handle node provisioning, scaling, and maintenance automatically for you.

2. Step 2: Understand Standard cluster management

   Standard clusters require you to create and manage nodes manually, including scaling and updates.

3. Final Answer:

   Autopilot manages the infrastructure automatically, while Standard requires manual node management. -> Option A

4. Quick Check:

   Autopilot = automatic node management [OK]

Hint: Autopilot means Google manages nodes for you [OK]

Common Mistakes:

• Thinking Standard clusters auto-scale nodes by default
• Confusing Autopilot with serverless functions
• Believing Autopilot only supports Windows nodes

2. Which of the following is the correct gcloud command to create a GKE Autopilot cluster named my-autopilot-cluster?

easy

A. gcloud container clusters create my-autopilot-cluster --mode=autopilot

B. gcloud container clusters create my-autopilot-cluster --enable-autopilot

C. gcloud container clusters create-autopilot my-autopilot-cluster

D. gcloud container clusters create my-autopilot-cluster --autopilot=true

Solution

1. Step 1: Recall the gcloud syntax for Autopilot clusters

   The correct command uses gcloud container clusters create with the flag --enable-autopilot.

2. Step 2: Check other options for correctness

   Options A, B, and D use incorrect commands or flags not supported by gcloud.

3. Final Answer:

   gcloud container clusters create my-autopilot-cluster --enable-autopilot -> Option B

4. Quick Check:

   Use --enable-autopilot flag to create Autopilot clusters [OK]

Hint: Use --enable-autopilot flag with create command [OK]

Common Mistakes:

• Using non-existent commands like create-autopilot
• Using incorrect flags like --mode=autopilot
• Assuming --autopilot=true is valid

3. Consider this snippet creating a Standard GKE cluster:

gcloud container clusters create my-standard-cluster \
  --num-nodes=3 \
  --machine-type=e2-medium

What will be the number of nodes and machine type in the cluster?

medium

A. Cluster creation will fail due to missing flags

B. 1 node with e2-medium machine

C. 3 nodes with default machine type

D. 3 nodes with e2-medium machines

Solution

1. Step 1: Analyze the command flags

   The flag --num-nodes=3 sets the cluster to have 3 nodes, and --machine-type=e2-medium sets the machine type for each node.

2. Step 2: Confirm cluster creation behavior

   Standard clusters accept these flags and create nodes accordingly without error.

3. Final Answer:

   3 nodes with e2-medium machines -> Option D

4. Quick Check:

   --num-nodes=3 and --machine-type=e2-medium create 3 e2-medium nodes [OK]

Hint: Flags --num-nodes and --machine-type set nodes and size [OK]

Common Mistakes:

• Assuming default node count is 1 despite --num-nodes flag
• Thinking machine type defaults if specified
• Believing cluster creation fails without extra flags

4. You tried to create an Autopilot cluster with this command:

gcloud container clusters create my-autopilot-cluster --num-nodes=3 --enable-autopilot

But it failed. What is the likely cause?

medium

A. Autopilot clusters require a zone flag.

B. You must specify --machine-type with Autopilot clusters.

C. Autopilot clusters ignore --num-nodes and fail if specified.

D. The cluster name is invalid for Autopilot clusters.

Solution

1. Step 1: Understand Autopilot cluster restrictions

   Autopilot clusters manage node count automatically and do not accept the --num-nodes flag.

2. Step 2: Identify why the command fails

   Including --num-nodes causes the command to fail because it conflicts with Autopilot's automatic management.

3. Final Answer:

   Autopilot clusters ignore --num-nodes and fail if specified. -> Option C

4. Quick Check:

   Do not use --num-nodes with Autopilot clusters [OK]

Hint: Autopilot ignores --num-nodes; remove it to fix [OK]

Common Mistakes:

• Adding --machine-type to Autopilot clusters
• Assuming cluster name causes failure
• Forgetting to specify zone (not mandatory)

5. You want to create a GKE cluster that automatically manages node scaling and maintenance but also allows you to customize node pools with specific machine types. Which cluster type should you choose and why?

hard

A. Standard cluster, because it allows full control over node pools and manual scaling.

B. Autopilot cluster, because it manages nodes automatically and allows node pool customization.

C. Autopilot cluster, because it requires manual node management but auto-scales pods.

D. Standard cluster, because it automatically manages nodes and does not allow customization.

Solution

1. Step 1: Identify Autopilot cluster features

   Autopilot clusters manage nodes automatically but do not allow customizing node pools or machine types.

2. Step 2: Identify Standard cluster features

   Standard clusters require manual node management but allow full customization of node pools and machine types.

3. Step 3: Match requirements to cluster type

   You want automatic node management plus node pool customization, which is not possible with Autopilot. Standard clusters allow customization but require manual scaling.

4. Final Answer:

   Standard cluster, because it allows full control over node pools and manual scaling. -> Option A

5. Quick Check:

   Customization needs Standard cluster; Autopilot limits node control [OK]

Hint: Customize nodes? Choose Standard; Autopilot limits control [OK]

Common Mistakes:

• Thinking Autopilot allows node pool customization
• Assuming Autopilot auto-scales nodes and pods separately
• Believing Standard clusters auto-manage nodes