Starts by default

Deploy real containers with the Cloud Run API.

Knative-backed services with revisions and scaling, plus jobs, worker pools and instances on Kubernetes workloads.

Backed by: Knative Serving for services; Kubernetes workloads for jobs and workers Knative

Get started
Local scope

What it covers

Cloud Run in CloudBurrow uses an API adapter in front of Knative Serving on the local kind cluster. Deploying a service starts a real container. Service-level scaling is written onto each revision and applied in place, and CloudBurrow’s CPU driver adds instances when the pods’ CPU passes the target. The WorkerPools and Instances clients exercise resources backed by Kubernetes Deployments. The verified source deploy path builds the image locally. Use the coverage table to see which API calls and runtime effects have a named test.

  • Create, get, list, update and delete services; inspect their revisions
  • Environment variables from Secret Manager
  • Min-instances is Verified; max-instances, concurrency, timeout and resource limits are mapped but not load-tested.
  • Service-level scaling: automatic with minimum and maximum, or manual instance counts; a scaling change creates no revision (#1790)
  • CPU autoscaling on cpuUtilization, driven by the pods' measured CPU, and concurrencyUtilization (#1790, #1800)
  • Disabled services: manual scaling with zero instances answers 503 Service unavailable while tag URLs keep serving (#1800, #1802)
  • Jobs and executions run as Kubernetes batch Jobs (#582)
  • Worker pools and standalone instances use Kubernetes Deployments, with worker-pool automatic scaling over REST (#1300, #1788)
  • Verified traffic splitting and revision tags using Knative (#1224)
  • Supported secret, in-memory, NFS, Cloud SQL and Storage FUSE volumes
  • Selected gcloud run commands, source deploys and Terraform resources, including the scaling block

In the console

A Cloud Run service and its revisions
Captured 2026-09-28 from main @5da2bd0. Product icons hidden.
Release and main

What's verified

Follow the operation matrix to see what the backend serves and the tests linked to Verified calls.

Cloud Run v2

41 of 46 RPCs Verified in v0.3.0

Cloud Run v2 in v0.3.0: 41 Verified of 46
Inspect the Cloud Run v2 operation matrix →

Cloud Run v1 (Knative API)

76 of 76 RPCs Verified in v0.3.0

Cloud Run v1 (Knative API) in v0.3.0: 76 Verified of 76
Inspect the Cloud Run v1 (Knative API) operation matrix →
Local boundaries

Not supported

  • 01 / Local boundary

    VPC access, encryption keys and other documented fields may be stored and returned with no runtime effect. Consult the mapping for each field.

  • 02 / Local boundary

    Traffic split tests exercise Knative routing. They do not establish Google's production distribution.

  • 03 / Local boundary

    A disabled service's 503 status code is CloudBurrow's reading: Google's page names no status code.

Evidence source

Source: docs/compatibility.md at main 0ea2594.

Frequently asked

Questions

What does the Cloud Run adapter map?

It maps supported service settings to Knative Serving. The compatibility table lists each tested mapping and identifies fields that are refused or stored without effect.
Link to this answer

Can I run Cloud Run Jobs?

Yes. Jobs and executions use Kubernetes batch Jobs. The official clients, selected gcloud commands and Terraform's google_cloud_run_v2_job are tested.
Link to this answer

Does service-level scaling work?

Yes. Service-level minimum, maximum and manual counts are divided among the serving revisions and applied by Knative in place. CPU utilization is measured on the pods and can add instances, as TestRunServiceCPUUtilizationScaling checks.
Link to this answer
Develop locally

Build against Google Cloud APIs, locally

Free and open source under Apache-2.0. No account, no sign-up, no Google Cloud bill.

Get started