---
title: "Comment by Mahdi Jabinpour on \"Cloud Run vs GKE: How I Actually Choose\" | Hashnode"
description: "The workload-first framework is useful. One branch needs an update, though: Cloud Run now supports GPUs, so a GPU requirement alone no longer makes GKE the defa"
url: "https://hashnode.com/posts/cloud-run-vs-gke-how-i-actually-choose/6adaca8706462334539f49ef/comment/6add11d0838a42a2d61b832e"
---

[Discussion](https://hashnode.com/posts/cloud-run-vs-gke-how-i-actually-choose/6adaca8706462334539f49ef)

Comment [Cloud Run vs GKE: How I Actually Choose](https://hashnode.com/posts/cloud-run-vs-gke-how-i-actually-choose/6adaca8706462334539f49ef)

[Mahdi Jabinpour](https://hashnode.com/@mahdi-lumowp)

[Oct 24](https://hashnode.com/posts/cloud-run-vs-gke-how-i-actually-choose/6adaca8706462334539f49ef/comment/6add11d0838a42a2d61b832e)

The workload-first framework is useful. One branch needs an update, though: Cloud Run now supports GPUs, so a GPU requirement alone no longer makes GKE the default answer. Google’s “GPU support for services” documentation covers the available configurations. I would make that decision depend on the accelerator, runtime and operational constraints rather than GPU versus no GPU.
