Changelog

Changelog.

On main, not yet released next release

Merged after v0.1.0; not in any release yet. Compare v0.1.0 with main

Added

A terminal in the console's top bar, like Cloud Shell (#781): Activate terminal opens a drawer with a shell in a pod in the instance's cluster (never on this machine), from the pinned Cloud SDK image with kubectl, with the instance's pod environment and gcloud configuration and no credential. It follows the toolbar's project, keeps its session across a closed drawer or a reload, and says why when there is no shell. The WebSocket is refused to any other origin, host or remote peer. What differs from Cloud Shell is in docs/compatibility.md.
A release is latest only once its smoke test has passed (#680): the release workflow publishes it as a prerelease, smoke-installs it on Linux and macOS, and only then marks it latest and pushes the formula to the Homebrew tap, so the install script, the action's version: latest and brew upgrade never get a release that failed it. docs/install.md says how to withdraw one.
A release is built only from a commit CI has passed (#596): the release workflow's first job requires a successful ci-green check for the tagged SHA, waiting up to 45 minutes while CI for it is still running, and fails with the SHA named before anything is built, pushed or published when there is none. docs/install.md describes it.
The macOS binaries can be signed and notarized (#605): the release workflow signs both darwin binaries with a Developer ID certificate (hardened runtime, secure timestamp) and notarizes them before the checksums, formula and attestations are computed. It is active only once the maintainer adds the Apple secrets; until then releases stay unsigned, and the release notes say which. docs/install.md explains how to verify, and what to do with an unsigned binary.
cloudburrow prefetch and up --offline (#604): prefetch stores in the state directory the kind node image, the storage image this CLI builds, every enabled backend's image by its pinned digest, Knative's YAMLs checked against their pinned sha256, and the images those YAMLs name. up prefers the cached copies; up --offline uses nothing else and, when something is missing, refuses before creating a cluster and names it. doctor reports whether each registry and GitHub is reachable, and whether the cache is complete. See "Offline and air-gapped use" in docs/install.md for the procedure, every artifact's measured size, and what is and is not tested. The Bigtable emulator no longer falls back to installing itself when its container starts.
The local-AI runtime image is published with each release (#602): ghcr.io/cloudburrow/litert-lm:<tag>, linux/amd64 and linux/arm64, attested, its digest in the release notes. A release CLI defaults --local-ai-image to that digest, so local generation no longer needs a checkout and make litert-lm.
CloudBurrow's own Cloud Storage server, built to the API rather than reused (ADR-0005 amendment, #486), and now the only Cloud Storage backend (#519). It serves buckets and objects over JSON, uploads including resumable and XML multipart, ranged reads, every precondition, objects.list with prefixes, offsets, globs and pages, compose, copy, rewrite and move, the batch endpoint, object versioning, soft delete and restore, retention policies, locks and holds, lifecycle rules, CORS, HMAC keys, notifications to Pub/Sub, the XML API subset, and signed URLs verified and failing closed (#489–#509). Bucket IAM policies are stored and never enforced (#504). It runs as a locally built image in one in-cluster Deployment (#514), with reset and seed (#510), state snapshots (#511), persistence by --mode (#512), events, metrics and faults (#513), and the console, status and request log (#518).
Cloud Storage verified through the official Python client (#516), gcloud storage and gsutil (#517) and Terraform (#515), and compared against Google's storage-testbench by a differential oracle (#497).
Cloud KMS through cloudburrow terraform (#425) and gcloud kms (#426, #427), and IAM policies stored on key rings and keys, never enforced, over gRPC and REST (#428–#431).
Cloud KMS automatic rotation (#816): rotation_period and next_rotation_time on CreateCryptoKey and UpdateCryptoKey, validated as resources.proto says (a period of 24 hours to 876,000 hours, and a next rotation time with it); at the next rotation time the key gets a new primary version and the time moves on by the period. The console's Edit key offers both.
A Cloud KMS oracle comparing the resource RPCs and the version lifecycle against a pinned fakekms, run nightly (#419, #420).
A release smoke test: after publishing, the release workflow installs the tag with the installer (checksum and attestation verified) on Linux and macOS, and installs, tests and strictly audits the Homebrew formula (#603).
This changelog, and SECURITY.md with how to report a vulnerability (#603).
RSA signed URLs verify on an up instance: the ADC fixture's key is registered with the storage server, and storage.signingCerts adds others (#577).

Changed

--mode ephemeral now also applies to Cloud KMS (#481) and Secret Manager (#483) state.
up creates the managed namespace whenever the cluster is up, not only with a backend (#571).
A Cloud Run revision that fails at startup is reported after 240s rather than Knative's 600s (#568).
Secret Manager refuses the create fields it would drop (ttl, rotation, topics and others), refuses list filters, compares request etags, and verifies and returns payload CRC32C (#580).
Cloud Tasks refuses OIDC and OAuth tokens, logging config and list filters it would drop, keeps dispatch_deadline and honours max_retry_duration (#578).
The embedded storage servers are no longer committed; make build and releases build them (#585).
Release notes are taken from this changelog instead of fixed text (#603).
The rendered Homebrew formula no longer sets a version that repeats the one in its URLs (#603).
A fault rule on Cloud Tasks' ListQueues, Secret Manager's ListSecrets or Cloud Scheduler's ListJobs now also fails that service's console list, with the message an SDK receives, and a console open on the screen draws from the rule's count (#594).
The console is tested in headless Chrome in CI (test/browser, chromedp): shell landmarks, the theme switch, creating a bucket through the form, the error card under an injected fault, keyboard row activation, and no request off loopback (#594). docs/console-verification.md describes the run in place of the manual transcript.

Fixed

A CLI built without the embedded Cloud Storage server (a plain go build or go install) is refused before up creates a cluster, naming the fix, rather than after kind has spent minutes creating one (#686). cloudburrow doctor and diagnose report it in an embedded storage row: which Linux builds are embedded and whether one is the node's. An empty or placeholder file counts as missing.
Port forwarding replaces a dead tunnel on evidence rather than on one client's failure (#526), retries a launch that does not carry (#572), and notices a pod that restarted its containers (#566).
The setup-cloudburrow action works with the CLI it installs (#679): it reads cloudburrow version --short and passes --trust and --port-base only to a CLI that has them, so version: v0.1.0 (and latest while that is v0.1.0) no longer fails with "flag provided but not defined". The port-base input with v0.1.0 fails before up, naming the version it needs. Installing any release through the action also failed before this ("The \"path\" argument must be of type string"): it looked for its own files in GITHUB_ACTION_PATH, which the runner sets only for composite actions. It now finds them from its own location, which also makes version: source build the action's checkout rather than the job's workspace. The action self-test also runs against the newest published release, and the release workflow runs it against each tag it publishes. docs/ci.md has the table.
Both Linux release archives are linked the same way (#714): every release CLI is built with CGO_ENABLED=0, and the release fails unless go version -m on each binary says so. The linux/amd64 binary was linked against the build runner's glibc; it is now static, like linux/arm64. Cloud Tasks and Cloud Scheduler HTTP targets under .localhost are dialled on 127.0.0.1 without a DNS lookup, so they no longer depend on the host's resolver. docs/install.md records the linkage and the measured resolver behaviour.
Container engines are stated, and an engine whose kind gateway is not on this machine fails early (#712): docs/install.md marks each engine supported, unverified or unsupported, with the evidence for each supported row. doctor names the engine from docker info and warns on rootless and non-Desktop VM engines, and no longer measures the host's / as the daemon root when a Linux client talks to Docker Desktop's VM. With Cloud Run, up checks that the kind gateway can be bound before relaying on it, and otherwise fails naming the engine and the workaround instead of with a bare listen error.

Security

Every /admin route now requires a per-instance token (#553).
Every HTTP listener refuses a request whose Host is not an IP address, localhost (or a name under .localhost), host.docker.internal, cloudburrow-host.<namespace>.svc.cluster.local or, on the builtin storage server, its Service and virtual-hosted bucket names, answering 421 with the rejected host named (#676). This is the DNS-rebinding defence: a page on a domain that resolves to 127.0.0.1 could otherwise drive the console and the service APIs as a same-origin peer. Cleartext HTTP/2, and so gRPC, is not checked, because a browser never sends it.
The builtin Cloud Storage server refuses a browser request from an origin that is neither loopback (localhost, *.localhost, 127.0.0.1, [::1], any port) nor named with the new up --cors-allow-origin (CLOUDBURROW_CORS_ALLOW_ORIGIN, config storage.corsAllowOrigins), answering 403 with no CORS headers, preflights included (#677). Its JSON API had allowed every origin, as Google's does, so any web page could read and change local buckets. A request with no Origin, as the SDKs and curl send, is unaffected. Access-Control-Allow-Credentials is no longer sent: no recorded observation of Google shows it.

0.1.0 · 2026-09-25

v0.1.0 on GitHub

The first release: a local Google Cloud emulator that runs in a local Kubernetes cluster and is driven through the official Google Cloud SDKs. What is and is not supported is recorded per operation in docs/compatibility.md and summarised in docs/status.md.

Added

A CLI and an owned local Kubernetes cluster: up, status, stop, reset, delete, env, doctor, logs, wait, up --detach, status --format json, diagnose, gcloud-setup and gcloud-teardown, and cloudburrow terraform (#53, #54, #89, #293, #305, #325, #326, #327, #331).
Services started by default: Cloud Storage, with notifications to Pub/Sub (#95); Pub/Sub, on Google's emulator; Cloud Tasks with HTTP dispatch and retry (#66, #67, #322); Cloud Run v2 backed by Knative Serving, including revisions and updates (#68, #299, #300); and Secret Manager over gRPC and JSON, backed by Kubernetes Secrets (#93, #94).
Opt-in services with --services: Firestore, Datastore, Bigtable and Spanner on Google's emulators (#75, #371); BigQuery on a community emulator (#323); Cloud SQL for PostgreSQL and MySQL data planes (#122, #297, #311); Memorystore on Valkey (#296); Cloud Scheduler (#302); Cloud Logging write and read (#304); and Cloud KMS with symmetric keys, Encrypt and Decrypt, the version lifecycle and REST transcoding (#385–#424). Cloud KMS is not a security boundary.
Resource Manager v1 and v3 projects (#298, #301), local credentials and a GCE metadata server (#92), and IAM Credentials token generation from the local signer (#303).
IAM policies stored, never enforced, on Secret Manager secrets and Cloud Tasks queues (ADR-0006, #308, #365, #366).
Vertex AI on local runtimes: a generateContent subset verified through the official genai SDK (#105, #106) and custom prediction containers (#90).
A local web console laid out after the Google Cloud console, with detail pages, actions where the backend supports them, SQL and query editors, Kubernetes views, metrics, a Logs Explorer and a request log (#97 onward).
An admin API for reset, seed and event inspection (#70, #317, #319, #320, #334), state save and load (#338, #340), lifecycle hooks (#333), fault injection (#306), request logging (#314), request metrics (#341) and OpenTelemetry traces (#313, #379).
The setup-cloudburrow GitHub Action (#330), env --format terraform and --format docker-compose (#332).
SDK compatibility suites for Go and Python (#56, #335), and per-service API coverage generated from the proto surface (#337).
Release packaging: archives for macOS and Linux on arm64 and amd64 with build attestations, one checksums.txt, a Homebrew formula and an installer that refuses an archive it cannot verify (#71, #324).

Rendered from CHANGELOG.md in cloudburrow/cloudburrow, synced 2026-09-28.

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