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. It also serves IAM, Cloud SQL and Memorystore admin APIs over real servers, and Firestore with MongoDB compatibility, none of which Google publishes an emulator for.

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

Link to this answer

Does state persist?

Persistence depends on the service and --mode. Explicitly save and load Pub/Sub configuration with cloudburrow state save and cloudburrow state load. Snapshots keep topics, subscriptions and schemas. Queued messages are excluded.

Source: docs/install.md (what survives a restart), test/compat/pubsubfollowups_test.go

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