--- title: Cloud Run vs. GKE: How to pick the platform that fits... description: Four practical tests decide between Google Cloud Run and GKE for a given workload. If your software never calls the Kubernetes API, needs scale-to-zero, has a... canonical: https://daily.dev/posts/cloud-run-vs-gke-how-to-pick-the-platform-that-fits-the-job-hrfxlsltm twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Cloud Run vs. GKE: How to pick the platform that fits the job | daily.dev og:description: Four practical tests decide between Google Cloud Run and GKE for a given workload. If your software never calls the Kubernetes API, needs scale-to-zero, has a... og:url: https://daily.dev/posts/cloud-run-vs-gke-how-to-pick-the-platform-that-fits-the-job-hrfxlsltm og:image: https://api.daily.dev/og/posts/HrFxLSLTm.png og:image:alt: Cloud Run vs. GKE: How to pick the platform that fits the job og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Cloud Run vs. GKE: How to pick the platform that fits the job **[All Things Open](https://daily.dev/sources/allthingsopen)** · 20 min read · 0 upvotes · 0 comments ## Summary Four practical tests decide between Google Cloud Run and GKE for a given workload. If your software never calls the Kubernetes API, needs scale-to-zero, has a container that fits the standard contract, and your team doesn't want to run a cluster, Cloud Run wins. GKE is the right call when you need Kubernetes objects like StatefulSets, DaemonSets, or Arm node control. The post walks through deploying a Gemini-powered quiz app, Explain It, on Cloud Run with `--min-instances 0 --max-instances 3 --cpu-boost`, Secret Manager for the API key, and GitHub Actions with Workload Identity Federation for CI/CD. GKE's cluster management fee runs $0.10 per cluster per hour, with one cluster per billing account covered by a $74.40 monthly credit. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Should I use Cloud Run or GKE for a stateless API with spiky traffic? Cloud Run is the better fit for a stateless web service or API with spiky traffic, including AI endpoints. It scales to zero when idle, requires no cluster management, and bills per request. GKE is the better choice only when the application needs Kubernetes-specific objects like StatefulSets, DaemonSets, custom resources, or in-cluster network policy across many dependent services. _daily.dev helps developers weighing Cloud Run against GKE track real deployment trade-offs before committing._ ### How much does a GKE cluster cost per month if it's mostly idle? GKE charges a cluster management fee of $0.10 per cluster per hour, which works out to running costs even when idle. One zonal or Autopilot cluster per billing account is covered by a monthly credit of $74.40, covering the fee for a single cluster running all month. A second cluster, or a regional Standard cluster, costs extra on top of that. _Budgeting a Kubernetes workload gets easier when cost details like this surface on daily.dev._ ### How do I deploy a container to Cloud Run with scale-to-zero and a max instance cap? Run `gcloud run deploy` with `--min-instances 0` to allow scale-to-zero and `--max-instances 3` (or your chosen cap) to bound cost, plus `--cpu-boost` to speed cold starts and `--execution-environment gen2`. Secrets can be injected with `--set-secrets GEMINI_API_KEY=gemini-api-key:latest` rather than baked into the image, keeping credentials out of build layers. _Developers shipping serverless containers can keep deployment flags like these handy via daily.dev._ ## Similar posts on daily.dev - [Introducing Cloud Run instances](https://daily.dev/posts/introducing-cloud-run-instances-lppkfdgfh) · Google Cloud · 0 upvotes · 0 comments - [Google Cloud Run Limitations: When Serverless Complexity Outweighs the Cost Savings](https://daily.dev/posts/google-cloud-run-limitations-when-serverless-complexity-outweighs-the-cost-savings-zafxsizzf) · Sergio Lema · 1 upvotes · 0 comments - [GKE Autopilot: How It Works, the Cost Model, and When It Saves](https://daily.dev/posts/gke-autopilot-how-it-works-the-cost-model-and-when-it-saves-ejdxeewma) · Cast AI · 1 upvotes · 0 comments - [Medium](https://daily.dev/posts/medium-vydqefujy) · Medium · 0 upvotes · 0 comments - [How platform teams are eliminating a $43,800 “hidden tax” on Kubernetes infrastructure](https://daily.dev/posts/how-platform-teams-are-eliminating-a-43-800-hidden-tax-on-kubernetes-infrastructure-lzn0volzl) · The New Stack · 0 upvotes · 0 comments --- Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#gcp](https://daily.dev/tags/gcp), [#github-actions](https://daily.dev/tags/github-actions), [#gke](https://daily.dev/tags/gke) [View this post on daily.dev](https://daily.dev/posts/cloud-run-vs-gke-how-to-pick-the-platform-that-fits-the-job-hrfxlsltm) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Cloud Run vs. GKE: How to pick the platform that fits the job","url":"https://daily.dev/posts/cloud-run-vs-gke-how-to-pick-the-platform-that-fits-the-job-hrfxlsltm","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/cloud-run-vs-gke-how-to-pick-the-platform-that-fits-the-job-hrfxlsltm"},"datePublished":"2026-10-26T06:52:37.345Z","dateModified":"2026-10-26T07:03:37.790Z","description":"Four practical tests decide between Google Cloud Run and GKE for a given workload. If your software never calls the Kubernetes API, needs scale-to-zero, has a...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ff8eac2ff88f46cdd06083f059bacaea?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ff8eac2ff88f46cdd06083f059bacaea?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"All Things Open","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"All Things Open","logo":"https://media.daily.dev/image/upload/s--dgFP6zAp--/f_auto/v1720885901/logos/allthingsopen","url":"https://daily.dev/sources/allthingsopen"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/cloud-run-vs-gke-how-to-pick-the-platform-that-fits-the-job-hrfxlsltm","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes,gcp,github-actions,gke","timeRequired":"PT20M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"All Things Open","item":"https://daily.dev/sources/allthingsopen"},{"@type":"ListItem","position":3,"name":"Cloud Run vs. GKE: How to pick the platform that fits the job"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/cloud-run-vs-gke-how-to-pick-the-platform-that-fits-the-job-hrfxlsltm#faq","mainEntity":[{"@type":"Question","name":"Should I use Cloud Run or GKE for a stateless API with spiky traffic?","acceptedAnswer":{"@type":"Answer","text":"Cloud Run is the better fit for a stateless web service or API with spiky traffic, including AI endpoints. It scales to zero when idle, requires no cluster management, and bills per request. GKE is the better choice only when the application needs Kubernetes-specific objects like StatefulSets, DaemonSets, custom resources, or in-cluster network policy across many dependent services. daily.dev helps developers weighing Cloud Run against GKE track real deployment trade-offs before committing."}},{"@type":"Question","name":"How much does a GKE cluster cost per month if it's mostly idle?","acceptedAnswer":{"@type":"Answer","text":"GKE charges a cluster management fee of $0.10 per cluster per hour, which works out to running costs even when idle. One zonal or Autopilot cluster per billing account is covered by a monthly credit of $74.40, covering the fee for a single cluster running all month. A second cluster, or a regional Standard cluster, costs extra on top of that. Budgeting a Kubernetes workload gets easier when cost details like this surface on daily.dev."}},{"@type":"Question","name":"How do I deploy a container to Cloud Run with scale-to-zero and a max instance cap?","acceptedAnswer":{"@type":"Answer","text":"Run `gcloud run deploy` with `--min-instances 0` to allow scale-to-zero and `--max-instances 3` (or your chosen cap) to bound cost, plus `--cpu-boost` to speed cold starts and `--execution-environment gen2`. Secrets can be injected with `--set-secrets GEMINI_API_KEY=gemini-api-key:latest` rather than baked into the image, keeping credentials out of build layers. Developers shipping serverless containers can keep deployment flags like these handy via daily.dev."}}]} ```