How CloudBurrow works.
Google's own emulators, Knative and CloudBurrow's own services in one local kind cluster, wired to the official SDKs, with local credentials that grant no Google Cloud access.
Get startedFollow a request through the local stack.
Start at the cluster, then trace the service mapping, local credentials and testing controls.
- Use familiar Kubernetes tools against the kind cluster.
- Follow each service to its emulator or implementation.
- See where local credentials and testing controls apply.
The local stack
- Cluster
- kind in Docker
- Cloud Run adapter
- Knative Serving
- Cluster tools
- kubectl and Helm
Go straight to the detail you need.
A real Kubernetes cluster underneath
cloudburrow up creates a kind cluster in Docker. It starts Google's own emulators where they exist and CloudBurrow's own services where they don't, then wires them together. Because it is real Kubernetes, kubectl, Helm charts and operators work against it directly.
Redrawn from How it fits together, in the README
at 0ea2594.
Reuse over rewrite
Google's own emulators are integrated, not reimplemented. CloudBurrow builds only where no upstream exists, and records the evidence for each choice, with the measurements behind it, in docs/upstream-evaluation.md.
Cloud Run on Knative
The Cloud Run v2 API is served by CloudBurrow's adapter, which maps each service onto Knative Serving in the cluster. The adapter refuses unsupported fields by name. It stores some settings, such as VPC access and encryption keys, without applying them.
The adapter also serves tested jobs, worker pools and standalone instances, which use Kubernetes batch Jobs or Deployments. Service-level scaling maps onto Knative's scale bounds, and worker-pool automatic scaling is driven on the pods' CPU utilization. Cloud Run: what is mapped, and what is refused
Credentials
cloudburrow env points tooling at a local ADC fixture and a GCE metadata server. A test fails if a
real ya29. token ever appears. IAM Credentials generateAccessToken and
generateIdToken come from a local signer, and no token grants any Google Cloud access.
IAM Credentials also serves signJwt and signBlob with each service
account's own key, and checks the caller's grants before it impersonates an account. Cloud Storage
verifies signed URLs against the instance's ADC key and those service accounts' certificates, so a URL
signed through signBlob works locally (#1787). A token or
signature made here verifies only against this instance's certificates.
Credentials and the local metadata server, in docs/credentials.md
Built for testing
Build against Google Cloud APIs, locally
Free and open source under Apache-2.0. No account, no sign-up, no Google Cloud bill.