CloudBurrow
Get started
Get started
Starts by default

Deploy real containers with the Cloud Run v2 API.

Services, revisions and jobs on the Cloud Run v2 API, run as real containers on Knative Serving.

Backed by: Knative Serving v1.23.0 behind a Cloud Run v2 adapter Knative

In the console

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

What it covers

Cloud Run in CloudBurrow is a Cloud Run v2 API adapter in front of Knative Serving on the local kind cluster. Deploying a service starts a real container, and your code calls it through the official Google client libraries. Knative is not Cloud Run: what the adapter maps is tested, and what it cannot map is refused with the field named.

  • Create, get, list, update and delete services; each update cuts a new revision
  • Revisions: get, list and delete
  • Environment variables from Secret Manager
  • Min-instances is Verified; max-instances, concurrency, timeout and resource limits are mapped but not load-tested.
  • Jobs and executions run as Kubernetes batch Jobs (#582); Terraform's google_cloud_run_v2_job applies over JSON (#591) next release
  • Prebuilt images only. gcloud run is untested.

What's verified

Cloud Run v2

8 of 41 RPCs Verified in v0.1.0

Cloud Run v2 in v0.1.0: 8 Verified of 41

18 of 41 RPCs Verified on main next release

Cloud Run v2 on main: 18 Verified of 41
Every Cloud Run v2 RPC, with its test →

Not supported

  • Refused, each with the field named: traffic splitting, service accounts, VPC, volumes, CMEK, Binary Authorization and session affinity
  • gcloud run is untested; gcloud run services list and gcloud run jobs use Cloud Run's v1 API, which is not served
  • HTTPS to a service: no certificate is issued

Source: docs/compatibility.md at main 82a2eb9.

Questions

Is it a full Cloud Run?
No. Knative is not Cloud Run. What the adapter cannot map is refused with the field named, never silently dropped.
Link to this answer

Can I run Cloud Run Jobs?
In the next release. On main, jobs and executions run as Kubernetes batch Jobs (#582), and Terraform's google_cloud_run_v2_job applies (#591). gcloud run jobs uses Cloud Run's v1 API, which is not served.
Link to this answer

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 View on GitHub
Get started