GKE vs Cloud Run decision in GCP - Quick Revision & Key Differences

Recall & Review

beginner

What is Google Kubernetes Engine (GKE)?

GKE is a managed service that lets you run and manage containers using Kubernetes, which helps you control many containers across multiple machines.

beginner

What is Cloud Run in Google Cloud?

Cloud Run is a service that runs your containerized apps without you managing servers. It automatically scales your app up or down based on traffic.

intermediate

When should you choose GKE over Cloud Run?

Choose GKE if you need full control over container orchestration, want to run complex workloads, or need to manage many containers with custom networking and storage.

intermediate

When is Cloud Run the better choice?

Cloud Run is better when you want to deploy quickly without managing infrastructure, need automatic scaling, and have stateless applications or microservices.

intermediate

What is a key difference in scaling between GKE and Cloud Run?

Cloud Run automatically scales to zero when no requests come in, saving costs. GKE requires you to manage scaling settings and resources.

Which service automatically scales your containerized app to zero when idle?

A GKE

B Compute Engine

C Cloud Run

D App Engine

Cloud Run automatically scales your app down to zero when there is no traffic, saving costs.

If you need full control over container orchestration and networking, which should you choose?

A Cloud Run

B GKE

C Cloud Functions

D Firebase Hosting

GKE gives you full control over container orchestration, networking, and storage.

Which service is best for quickly deploying stateless microservices without managing servers?

A Cloud Run

B BigQuery

C Compute Engine

D GKE

Cloud Run lets you deploy stateless microservices quickly without managing infrastructure.

Which service requires you to manage scaling policies and cluster resources?

A Cloud SQL

B Cloud Run

C Cloud Storage

D GKE

GKE requires you to configure and manage scaling and cluster resources.

Which service is serverless and abstracts away infrastructure management?

A Cloud Run

B Compute Engine

C GKE

D Kubernetes Engine

Cloud Run is serverless and handles infrastructure management for you.

Explain the main differences between GKE and Cloud Run and when to use each.

Think about control, complexity, and scaling.

Describe how scaling works differently in GKE versus Cloud Run.

Focus on automatic versus manual scaling.

Practice

1. Which service should you choose if you want to avoid managing servers and focus only on deploying containers?

easy

A. Compute Engine

B. Google Kubernetes Engine (GKE)

C. App Engine Standard

D. Cloud Run

Solution

1. Step 1: Understand server management needs

   Cloud Run is serverless, so it handles server management automatically.

2. Step 2: Compare with GKE

   GKE requires managing Kubernetes clusters and nodes, which means more management effort.

3. Final Answer:

   Cloud Run -> Option D

4. Quick Check:

   Serverless = Cloud Run [OK]

Hint: Serverless means no server management needed [OK]

Common Mistakes:

• Confusing GKE as serverless
• Choosing Compute Engine which is VM-based
• Thinking App Engine Standard is container-focused

2. Which of the following is the correct way to deploy a container image to Cloud Run using gcloud CLI?

easy

A. gcloud run deploy SERVICE --image IMAGE_URL --platform managed

B. gcloud container clusters create SERVICE --image IMAGE_URL

C. gcloud compute instances create SERVICE --image IMAGE_URL

D. gcloud app deploy --image IMAGE_URL

Solution

1. Step 1: Identify Cloud Run deployment command

   The correct command uses gcloud run deploy with the service name and image URL.

2. Step 2: Eliminate other commands

   Other options relate to Kubernetes clusters, VM instances, or App Engine, which are incorrect for Cloud Run.

3. Final Answer:

   gcloud run deploy SERVICE --image IMAGE_URL --platform managed -> Option A

4. Quick Check:

   Cloud Run deploy uses gcloud run deploy [OK]

Hint: Cloud Run deploy always uses 'gcloud run deploy' [OK]

Common Mistakes:

• Using 'gcloud container clusters create' for Cloud Run
• Confusing Compute Engine commands with Cloud Run
• Using App Engine deploy command for Cloud Run

3. You deploy a containerized app to GKE with autoscaling enabled. What happens when traffic suddenly spikes?

medium

A. Cloud Run automatically pauses the service until traffic decreases.

B. GKE automatically adds more pods to handle the increased load.

C. GKE shuts down pods to save resources during high traffic.

D. Cloud Run requires manual scaling to handle traffic spikes.

Solution

1. Step 1: Understand GKE autoscaling behavior

   GKE uses Horizontal Pod Autoscaler to add pods automatically when traffic increases.

2. Step 2: Compare with Cloud Run behavior

   Cloud Run scales automatically but does not pause services; manual scaling is not required.

3. Final Answer:

   GKE automatically adds more pods to handle the increased load. -> Option B

4. Quick Check:

   GKE autoscaling adds pods on traffic spike [OK]

Hint: GKE autoscaling adds pods automatically on load [OK]

Common Mistakes:

• Thinking Cloud Run pauses services on high traffic
• Believing GKE shuts down pods during spikes
• Assuming Cloud Run needs manual scaling

4. You tried deploying a container to Cloud Run but got an error about missing CPU allocation. What is the likely cause?

medium

A. You did not specify the CPU limit in the deployment command.

B. Cloud Run does not support containers with CPU requirements.

C. You deployed to GKE instead of Cloud Run by mistake.

D. The container image is not compatible with Cloud Run.

Solution

1. Step 1: Understand Cloud Run CPU allocation

   Cloud Run requires CPU allocation settings; missing these can cause errors.

2. Step 2: Check deployment command

   If CPU limits are not specified, Cloud Run deployment fails with CPU allocation errors.

3. Final Answer:

   You did not specify the CPU limit in the deployment command. -> Option A

4. Quick Check:

   Missing CPU limit causes deployment error [OK]

Hint: Always specify CPU limits when deploying to Cloud Run [OK]

Common Mistakes:

• Assuming Cloud Run ignores CPU settings
• Confusing GKE deployment with Cloud Run
• Blaming container image compatibility without checking CPU

5. Your team needs to run a complex microservices app with custom networking, persistent storage, and fine-grained control over scaling. Which service is best?

hard

A. Cloud Run because it handles all scaling automatically

B. Cloud Functions because it runs code without servers

C. GKE because it supports complex orchestration and custom setups

D. App Engine because it is fully managed and simple

Solution

1. Step 1: Analyze app requirements

   The app needs complex orchestration, custom networking, persistent storage, and detailed scaling control.

2. Step 2: Match requirements to services

   GKE supports Kubernetes features for complex setups, while Cloud Run is simpler and serverless but less customizable.

3. Final Answer:

   GKE because it supports complex orchestration and custom setups -> Option C

4. Quick Check:

   Complex control needs = GKE [OK]

Hint: Complex apps with custom needs use GKE [OK]

Common Mistakes:

• Choosing Cloud Run for complex networking
• Confusing App Engine with container orchestration
• Using Cloud Functions for microservices orchestration