GKE cluster creation (Autopilot vs Standard) in GCP - Visual Side-by-Side Comparison

Process Flow - GKE cluster creation (Autopilot vs Standard)

Start: Choose cluster mode

↓

Autopilot Mode

↓

Google manages nodes

↓

User deploys pods

↓

Billing per pod resource

↓

Cluster ready

↓

Standard Mode

↓

User manages nodes

↓

User configures node pools

↓

User deploys pods

↓

Billing per node

↓

Cluster ready

The flow starts by choosing Autopilot or Standard mode. Autopilot means Google manages nodes and bills per pod resources. Standard means user manages nodes and bills per node.

Execution Sample

GCP

gcloud container clusters create-auto my-autopilot-cluster --region=us-central1

gcloud container clusters create my-standard-cluster --region=us-central1 --num-nodes=3

Creates one Autopilot cluster where Google manages nodes, and one Standard cluster where user manages 3 nodes.

Process Table

Step	Action	Cluster Mode	Node Management	Billing Model	Result
1	Start cluster creation	N/A	N/A	N/A	Decide Autopilot or Standard
2	Run 'create-auto' command	Autopilot	Managed by Google	Per pod resource	Cluster provisioning starts
3	Cluster nodes auto-provisioned	Autopilot	Managed by Google	Per pod resource	Nodes created automatically
4	User deploys pods	Autopilot	Managed by Google	Per pod resource	Pods run on managed nodes
5	Cluster ready	Autopilot	Managed by Google	Per pod resource	Cluster ready for use
6	Run 'create' command with node count	Standard	User manages nodes	Per node	Cluster provisioning starts
7	User node pools created	Standard	User manages nodes	Per node	Nodes created as specified
8	User deploys pods	Standard	User manages nodes	Per node	Pods run on user nodes
9	Cluster ready	Standard	User manages nodes	Per node	Cluster ready for use
10	End	N/A	N/A	N/A	Cluster creation complete

💡 Both cluster types reach ready state; difference is in node management and billing.

Status Tracker

Variable	Start	After Autopilot Creation	After Standard Creation	Final
Cluster Mode	None	Autopilot	Standard	Both created
Node Management	None	Managed by Google	User manages nodes	Set per mode
Billing Model	None	Per pod resource	Per node	Set per mode
Nodes	0	Auto-provisioned	User provisioned (3)	Nodes exist
Pods	0	User deploys pods	User deploys pods	Pods running

Key Moments - 3 Insights

Why does Autopilot not require me to specify node count?

Because in Autopilot mode, Google manages nodes automatically (see execution_table step 3), so you only deploy pods and pay per pod resource.

How is billing different between Autopilot and Standard?

Autopilot bills per pod resource usage, while Standard bills per node regardless of pod usage (see execution_table steps 4 and 8).

Who is responsible for node maintenance in Standard mode?

In Standard mode, the user manages and maintains nodes and node pools (see execution_table step 7), unlike Autopilot where Google handles it.

Visual Quiz - 3 Questions

Look at the execution_table at step 3, who manages the nodes in Autopilot mode?

A Nodes are not created

B User manages nodes manually

C Google manages nodes automatically

D Billing is per node

💡 Hint

Check the 'Node Management' column at step 3 in execution_table

At which step does the Standard cluster create user-managed nodes?

A Step 4

B Step 7

C Step 2

D Step 9

💡 Hint

Look for 'User node pools created' action in execution_table

If you want Google to handle node maintenance, which cluster mode should you choose?

A Autopilot

B Standard

C Both modes

D Neither mode

💡 Hint

Refer to 'Node Management' differences in variable_tracker

Concept Snapshot

GKE cluster creation has two modes:
- Autopilot: Google manages nodes, billing per pod resource, no node config needed.
- Standard: User manages nodes, billing per node, user configures node pools.
Choose Autopilot for simplicity, Standard for control.
Commands differ: 'create-auto' vs 'create'.

Full Transcript

This visual execution shows how to create GKE clusters in Autopilot and Standard modes. First, you choose the mode. Autopilot clusters have nodes managed by Google, automatically created and billed per pod resource. Standard clusters require you to manage nodes and node pools, billing per node. The execution table traces steps from starting creation to cluster ready state for both modes. Variables track cluster mode, node management, billing, nodes, and pods. Key moments clarify why Autopilot hides node details, billing differences, and node maintenance responsibilities. The quiz tests understanding of node management and billing differences. The snapshot summarizes key points for quick recall.

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