OperatorsProduction operations

Production operations

Operate the hosted broker on GCP with regional Cloud SQL, Secret Manager, HTTPS, monitoring, backups, and controlled releases.

Operator-only material

Application teams do not need a database URL or GCP access. They receive a scoped service credential and the public broker URL.

Production topology

  • Google Cloud HTTPS load balancer with managed TLS certificate.
  • Broker containers on a Compute Engine VM.
  • Cloud SQL Auth Proxy between the broker and PostgreSQL.
  • Clerk OAuth for hosted human MCP access.
  • Google Secret Manager for broker and database credentials.

Database

Production uses PostgreSQL 16 in a regional Cloud SQL configuration spanning two zones. Automated backups and point-in-time recovery are enabled. The database stores resource catalog records, service credentials and hashes, service versions and heartbeats, probes, statuses, retained events, source maps, and audit events.

Clients never receive DATABASE_URL. The broker is the only public data access boundary.

Secrets

Secret Manager contains the shared break-glass key ring, PostgreSQL password, and Clerk backend secret. Non-secret Clerk origins and the publishable key are deployment configuration.

Deploy

shell
PROJECT_ID="<gcp-project>" \
DATABASE_BACKEND=cloud-sql \
CLOUD_SQL_AVAILABILITY_TYPE=regional \
HTTPS_DOMAIN=liveprobe.tryastrea.tech \
deploy/gcp/deploy.sh

Deploy only a clean, tested Git revision. The script builds on the VM, waits for container health, and reports the exact deployed SHA. Preserve all Clerk production configuration when redeploying.

Monitoring

Monitor broker readiness, load-balancer 5xx responses, VM and container health, Cloud SQL connectivity, storage, and backup age. Smoke tests should not intentionally generate 5xx responses because they create false incidents.