FAQ

Architecture

Why Kubernetes, how it relates to gcloud emulators, and state.

Why Kubernetes instead of a single binary?

Cloud Run deploys real containers on Knative, and kubectl, Helm and operators work on the same cluster.

Source: README.md, docs/upstream-evaluation.md

Link to this answer

How is this different from gcloud emulators?

It runs those same Google emulators for Pub/Sub, Firestore, Datastore, Bigtable and Spanner, and adds Cloud Run, Storage, Tasks, Secret Manager, KMS, Scheduler, Logging, credentials and a console around them.

Source: docs/status.md (per service), docs/compatibility.md (optional services)

Link to this answer

Does state persist?

It depends on --mode ephemeral|persistent and on the service. Pub/Sub never survives a restart; see "What is not persisted" in docs/install.md.

Source: docs/install.md (what is not persisted), docs/status.md (what will not work and why)

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