Diagram
A decision tree that branches first on needing full OS or kernel control plus any GPU or TPU (Compute Engine), then on Kubernetes orchestration, stateful or persistent-volume needs (GKE), and finally on stateless request-driven, event-driven, or batch work (Cloud Run).
Choosing Between GKE and Cloud Run
Choosing between GKE and Cloud Run depends on application type, control needs, and cost pattern. GKE fits when deep Kubernetes control, custom networking, persistent storage, or complex orchestration is required, while Cloud Run fits when simplicity, automatic request-driven scaling, and minimal operations are required.
| Feature | GKE | Cloud Run |
|---|---|---|
| Deployment and management | User manages clusters, including nodes, networking, scaling, and upgrades | No cluster to manage; provide source or image and Google builds and runs it |
| Control and flexibility | Full control over node configuration, network policies, security, and add-ons | Limited infrastructure control; configure environment variables, concurrency, and connections |
| Application types | Stateless and stateful apps with specific resource needs | Stateless, request-driven services, APIs, and batch jobs |
| Pricing model | Pay-per-cluster per hour | Pay-per-use, rounded up to nearest 100 milliseconds |
Domain 1 of 11
24 practice questions
Practice this DomainLast updated