Orkestia
Blog
Runners

Cloud Run

Runner group kind backend_type=cloud_run — Google Cloud Run Jobs (beta)

backend_type: cloud_run. Connection: GCP. Status: beta.

Each execution is a Cloud Run Job in a region you name. Serverless burst on GCP; no GCE VM to size.

When to choose it

  • GCP-resident work that fits a container job (CI or agent).
  • Scale-to-zero between executions.

Choose GCE when you need a VM, local disk, or apt-based startup.

Connection

A GCP connection. Image pull uses the project's artifact permissions — see the GCP runner image-pull notes in operations docs if jobs fail at start.

Required config

KeyTypeMeaning
project_idstringGCP project for the jobs.
regionstringCloud Run region (e.g. us-central1).

Optional knobs

container_image (registry mirror when omitted), service_account.

Execution control

Suffixed workflows: runner.execution-{stop,restart,sync,logs-sync}-cloud-run, plus a -generic restart variant.

Beta. Treat auto-reap and warm-pool convergence as partial until the catalog shows a runner.pool-reconcile-cloud-run (or equivalent) you actually run.