Deploy on Google Cloud Run

When you finish this page, the Kindgi runtime runs on Cloud Run in one Google Cloud project, with a pack orchestrator that gives each deployment of your pack a Cloud Run service of its own, and everything around them, from Kindgi's Terraform module. You then deploy your pack, run a flow, and turn on sign-in. The Cloud Run module reference has what the module grants, the settings that change its shape, and its limits.

In the verification run, made with the module's earlier single pack service, the first apply took about ten minutes, most of it Cloud SQL. A tool call from the runtime to your pack took 42 ms at the median, and 100 ms at p95.

Access to the runtime image

Sign in at access.kindgi.com with GitHub or your email address for a license key. The key is also the runtime image's password (Pull the runtime image). Questions or trouble: contact@kindgi.com.

What you'll have

• The runtime (kindgi-server): Kindgi's server, on Cloud Run with its own service account and one instance. It has public ingress on port 4000, which Cloud Run passes as PORT. Its CPU is always allocated, so a run started in the background keeps running after its answer.
• The pack orchestrator (kindgi-pack-orchestrator): a Cloud Run Job from the runtime's image, which Cloud Scheduler runs once a minute. Each pass makes a Cloud Run service for each deployment of your pack that needs one, gives running ones their changed env, and retires what should go (Turn on the pack orchestrator).
• A pack service for each deployment (kp-…): that deployment's tools' code (Your tools' code). Each tool call goes to the newest deployment in the run's project that shipped the version it names, so an earlier version runs from the deployment that shipped it (Agent and tool versions). Internal ingress, and IAM-protected: the runtime calls it with a Google ID token and the service's own token. Its CPU is allocated only while a call runs. A service scales to zero when it's idle, and its first call after that waits for an instance to start (Your pack services).
• Cloud SQL (Postgres 16) for the runtime's data, reached through the Cloud SQL socket, which encrypts the connection and checks the server (Check the database's certificate).
• Artifact Registry for the runtime's image and your pack's. The runtime also reads your pack's image from it when you deploy.
• Secret Manager for the runtime's secrets, and a Cloud KMS key that wraps the secrets the runtime stores, such as model API keys and webhook secrets, and each pack service's token.
• A VPC with Direct VPC egress and Cloud NAT, which carries the runtime's calls to your pack services and out to model APIs and webhooks. Or, when your tools need a VPC you already have, that VPC through its connector (A new VPC, or yours).

Your organization may forbid public access to Cloud Run: its iam.allowedPolicyMemberDomains policy then refuses allUsers. Set server_invoker_iam_disabled = true and server_public = false. The runtime's API token still guards every call.

Who calls whom:

• your app calls the runtime, with its API token;
• the runtime calls each deployment's pack service, with a Google ID token and the service's own token, and Cloud SQL and model APIs;
• the pack orchestrator calls the runtime's system routes, with a key of its own, and Cloud Run and Secret Manager, to make and retire the pack services and their tokens;
• kindgi deploy calls the runtime with a signed envelope, and the runtime reads the pack's image from Artifact Registry.

Before you start

• A Google Cloud project, and a Cloud Storage bucket for Terraform's state. Whoever applies the module is an Owner, or an Editor with Security Admin and Secret Manager Admin. Use a project of its own for each deployment (Staging and production).
• A region with Cloud Scheduler: the orchestrator's schedule is made in the module's region (Cloud Scheduler locations). Some Cloud Run regions have none, such as us-east5, europe-north1 and australia-southeast2, and the schedule can't be made there.
• Terraform 1.6 or later, gcloud, Docker with buildx, jq, curl, openssl, and your pack's kindgi CLI, 0.1.2 or later, which has kindgi key trust.
• For kindgi commands: Kindgi 0.2's CLI, which runs from any folder as npx --yes @kindgi/cli@0.2 (Install). Inside a pack project, pnpm exec kindgi runs the project's pinned CLI instead. The build, env plan and deploy steps need the pack's folder, so they use pnpm exec kindgi.
• Runtime 0.1.1 or later. Cloud SQL has no superuser; 0.1.0 can't start on it.
• A license key: a non-production key covers staging, and it also pulls the runtime image. Get one at access.kindgi.com, or from contact@kindgi.com.
• Docker logged in to registry.kindgi.com with that key (Pull the runtime image).
• A pack that kindgi build --local --push builds, with an environment block for this deployment in its config.

1. The foundation

The services need images and secret values that the next steps make. So the first apply creates everything else: the APIs, the network, the service accounts, the repository, the KMS key, Cloud SQL and the secrets' containers.

The module is deploy/gcp-cloud-run/ in the kindgi-sdk repository: copy the folder from the release you run. Its README.md lists every variable. example.tfvars is the shape on this page, with a new VPC. example-connector.tfvars runs in a VPC you already have, through a Serverless VPC Access connector. A new VPC, or yours says which to pick.

cp example.tfvars prod.tfvars   # project_id, region, kindgi_env, the seed ids, …
terraform init -backend-config=bucket=<state bucket> -backend-config=prefix=<this deployment>
terraform apply -var-file=prod.tfvars \
  -target=google_project_service.apis \
  -target=google_compute_router_nat.nat \
  -target=google_artifact_registry_repository_iam_member.server_reads_images \
  -target=google_kms_crypto_key_iam_member.server_wraps \
  -target=google_sql_database.kindgi \
  -target=google_secret_manager_secret_iam_member.server_reads \
  -target=google_project_iam_member.server_sql_client

Excerpt

• prod.tfvars holds this deployment's variables. example.tfvars lists them.
• -backend-config tells init where the state goes: <state bucket>, and <this deployment> as its own prefix in it.
• -target limits this apply to the APIs, the network, the database, the secrets' containers and the grants, with what they need.

Give each deployment its own state prefix, never shared with your app's own infrastructure.

server_image needs only a digest-shaped placeholder here, since the services aren't in this apply. Of what the plan creates, Cloud SQL is the long one, about six minutes.

The module sets Cloud SQL's edition to ENTERPRISE. A Postgres 16 instance otherwise defaults to ENTERPRISE_PLUS, which takes only the db-perf-optimized-N-* tiers, and the apply fails with Invalid Tier (db-f1-micro) for (ENTERPRISE_PLUS) Edition.

2. The images into Artifact Registry

Cloud Run pulls from Artifact Registry. It can't pull from registry.kindgi.com, which takes your license key as its password. With Docker logged in there, copy the runtime image into Artifact Registry by digest, with every platform it was built for:

REPO=$(terraform output -raw image_repository)
gcloud auth configure-docker "${REPO%%/*}"
docker buildx imagetools create --tag "$REPO/runtime:0.3.0" \
  registry.kindgi.com/kindgi/runtime:0.3.0@sha256:1f5cfe0032bb82b467781949978719d6a3da4d500cd994471f2f2e009c9a1b9f

• REPO is the repository's address, from the foundation's output. configure-docker lets Docker push to its host.
• imagetools create --tag copies the image by digest, every platform included, under the tag you give.

The copy keeps the release's digest. A plain docker pull, tag and push from an Apple silicon machine pushes only the arm64 image, which Cloud Run can't run.

The copy goes through the machine you run it on, every layer down and back up, and takes both platforms (amd64 and arm64), so on a slow uplink it can take most of an hour.

A repository you already have instead of the module's own: image_repository = { project, location, repository }. The module then creates none, gives the runtime's service account and the pack orchestrator's roles/artifactregistry.reader on it, and, for a repository in another project, gives this project's Cloud Run service agent the same role so it can pull. terraform output image_repository names where images go, either way.

Check the repository's cleanup policies

A cleanup policy that deletes tags or images by age can delete the digest a running revision pins, and the next instance start then fails. Keep Kindgi's images out of such a policy, or use the module's own repository.

Then build and push your pack's image, signed. --local builds it on your machine, --push pushes it to the registry of your pack's prod environment block, and --env prod names that block:

pnpm exec kindgi build --local --push --env prod

It prints the build as JSON, then each step. The last steps:

…
    ✓ Pushed …/acme@sha256:bd7bfe4f…

  Verifying build output
    ✓ /app/index.json in the image matches the local index byte for byte

  Signing locally
    ✓ Ed25519 signature over (imageDigest, artifactVersion, indexHash, tenantId, publishedAt)
      key: …
…

Excerpt

Set server_image in prod.tfvars to the runtime's digest (…@sha256:…). The pack orchestrator runs from the same image.

Your pack's image needs no variable: kindgi deploy (5. Trust your key, and deploy) registers the image kindgi build pushed, and the orchestrator runs that deployment's service from it.

3. The secrets

The services read their secrets from Secret Manager. Make each value here and pipe it straight into Secret Manager: it's never on disk, in Terraform's state or in a command's arguments, which other processes can read and gcloud writes to its log file. Kindgi generates none of them. The commands are for bash or zsh. To run with no KMS key, set secrets_backend = "none" first (Without a KMS key).

N=kindgi   # name_prefix
CONN=$(terraform output -raw sql_connection_name)
P=$(gcloud config get-value project)

# Kindgi's database user: a built-in user, not an IAM one. The instance is
# named after name_prefix ($N); the database is database_name (kindgi).
# Made through the Cloud SQL Admin API rather than `gcloud sql users create --password`:
# the body goes in on stdin and the token in a header from a pipe.
# Each step runs only if the one before it worked, so the secret never holds
# a password the user wasn't given.
DBPW=$(openssl rand -hex 24)
OP=$(printf '{"name":"kindgi","password":"%s"}' "$DBPW" \
  | curl -sS -H @<(printf 'Authorization: Bearer %s\n' "$(gcloud auth print-access-token)") \
      -H 'Content-Type: application/json' --data-binary @- \
      "https://sqladmin.googleapis.com/v1/projects/$P/instances/$N/users" \
  | jq -r '.name // error(.error.message)') && [ -n "$OP" ] \
  && gcloud sql operations wait "$OP" --project=$P \
  && printf 'postgres://kindgi:%s@/kindgi?host=/cloudsql/%s' "$DBPW" "$CONN" \
  | gcloud secrets versions add $N-database-url --data-file=-
unset DBPW

# The first API token, and the two keys, base64.
printf 'kgi_bt_%s' "$(openssl rand -hex 32)" | gcloud secrets versions add $N-api-token --data-file=-
openssl rand 32 | base64 | gcloud secrets versions add $N-secrets-aad-key --data-file=-   # version 1 (not with secrets_backend = "none")
openssl genpkey -algorithm ed25519 | base64 | gcloud secrets versions add $N-public-token-key --data-file=-
# Only with export_signing = "secret": the key that signs exports.
openssl genpkey -algorithm ed25519 | base64 | gcloud secrets versions add $N-export-signing-key --data-file=-

# The license key, pasted, never echoed.
read -rs LICENSE_KEY && printf '%s' "$LICENSE_KEY" | gcloud secrets versions add $N-license-key --data-file=- && unset LICENSE_KEY

• N is your name_prefix, CONN the Cloud SQL instance's connection name, and P your Google Cloud project's id.
• curl sends the database user's name and password to the Cloud SQL Admin API (users.insert) on its input, with your gcloud access token in a header read from a pipe. jq takes the operation's name, or prints the API's error, and gcloud sql operations wait waits until the user exists. The &&s stop at the first step that fails, and [ -n "$OP" ] stops them when curl got no answer: then no password goes into the secret.
• gcloud secrets versions add <name> --data-file=- adds what it reads on its input as the secret's next version.
• openssl rand makes random values, and openssl genpkey -algorithm ed25519 an Ed25519 private key.
• read -rs reads the license key you paste, without showing it.

The server reads the AAD key's version that secrets_aad_key_version names in prod.tfvars: "1", the one you added. The example files have it. Every secret stored in Postgres is bound to that key, so the module pins it and refuses latest:

secrets_aad_key_version is a version number ("1" for a new deployment), never "latest": every secret stored in Postgres is bound to the key it names.

The database user is a built-in Cloud SQL user. It isn't a superuser. But it has CREATEROLE, and owns the database through cloudsqlsuperuser, which is what the runtime needs. An IAM database user has neither.

Your pack's own secrets aren't Terraform's. Each deployment's pack service gets its env from the runtime: the names your pack declares, with the values you set through Kindgi (Your pack's env). A secret of yours in Secret Manager that the pack's env names goes in pack_secret_readers (Read a secret of yours).

4. The services

With the runtime's image and the secrets in place, apply the whole module. It creates the runtime's service, and the pack orchestrator's account, its grants and the secret for its key:

terraform apply -var-file=prod.tfvars

On Cloud Run the runtime logs JSON, so its startup lines are the lines of one log record, Kindgi runtime ready:

gcloud logging read 'resource.labels.service_name="'$N'-server" AND jsonPayload.message="Kindgi runtime ready"' \
  --limit=1 --format=json | jq -r '.[0].jsonPayload.lines[]'

--limit=1 reads the newest such record, and jq prints its lines. One of them names how the runtime reaches your pack's code (How the runtime calls your pack services):

Pack services: one per deployment, at the endpoints recorded through the system API (1 allowed host pattern), each endpoint's token sealed under KINDGI_PACK_ENDPOINT_KMS_KEY's key

The module sets the runtime to send each tool call to its deployment's own pack service (KINDGI_PACK_ROUTING=per-deployment), at a Cloud Run URL of this project and region (KINDGI_PACK_ENDPOINT_HOSTS = "*-<project number>.<region>.run.app"). Each service's token is sealed under the module's KMS key (KINDGI_PACK_ENDPOINT_KMS_KEY). It also lets a pack's env name a secret of yours in Secret Manager, a cloud secret (KINDGI_ENV_CLOUD_SECRETS=on). server_env and server_secret_env can't set these. No deployment has a service until the pack orchestrator is on.

The KMS checks come right before, as log lines of their own: one for the pack services' tokens, and with secrets_backend = "postgres" one for the store:

gcloud logging read 'resource.labels.service_name="'$N'-server" AND textPayload:"KMS probe"' \
  --limit=2 --format='value(textPayload)'

Pack endpoint KMS probe OK (gcp-cloud-kms): gcp-cloud-kms v1 (encrypt/decrypt round trip, key version 1) (160ms)
KMS probe OK (gcp-cloud-kms): gcp-cloud-kms v1 (encrypt/decrypt round trip, key version 1) (170ms)

Turn on the pack orchestrator

The pack orchestrator is a Cloud Run Job, $N-pack-orchestrator, from the runtime's image. It runs kindgi-runtime packs orchestrate as its own account, $N-orch, and Cloud Scheduler starts it once a minute. Each pass makes a service for each deployment that needs one, gives running ones their changed env, and retires what should go, through the runtime's system routes. The runtime never makes or deletes a service itself. Run a pack service for each deployment on Cloud Run says what a pass does and what each of its settings means.

The orchestrator works with a system key of its own, which only a runtime that already routes per deployment mints. So it takes a second apply. The first made the orchestrator's account, its grants and the $N-orchestrator-key secret. Until the second, terraform output orchestrator_key_steps prints these steps, with your names in them.

1. Mint the key with the API token, and add it as the first version of $N-orchestrator-key:

   URL=$(terraform output -raw server_url)
   KEY=$(curl -sS -X POST "$URL/v1/system/keys" \
     -H @<(printf 'Authorization: Bearer %s\n' "$(gcloud secrets versions access latest --secret=$N-api-token)") \
     -H 'Content-Type: application/json' -H "Idempotency-Key: $(uuidgen)" \
     -d '{"scopes": ["system:deployments", "system:pack-env"], "label": "pack orchestrator"}' \
     | jq -j '.token // error(.error.message)') && [ -n "$KEY" ] \
     && printf '%s' "$KEY" | gcloud secrets versions add $N-orchestrator-key --data-file=-
   unset KEY

   • curl asks the runtime for a system key that may manage each deployment's service and read its env, with the API token in a header read from a pipe.
   • jq -j keeps only the key, with no newline, or prints the API's error.
   • The version is added only if a key came back: a refused or failed call adds none. printf is built into the shell, so the key stays off the command line.

   With the runtime behind Cloud Run IAM (server_public = false without server_invoker_iam_disabled), your gcloud account needs roles/run.invoker on the runtime's service, and the call needs its ID token too. Add this line after the curl line:

     -H @<(printf 'X-Serverless-Authorization: Bearer %s\n' "$(gcloud auth print-identity-token)") \

2. Set orchestrator_key_version = "1" in prod.tfvars, the version gcloud printed, and apply again:

   terraform apply -var-file=prod.tfvars

   That makes the Job and its schedule, and orchestrator_key_steps is null from then on. The module refuses latest: a version added by mistake must not reach the Job.

Then deploy your pack (5. Trust your key, and deploy). A new deployment waits up to about a minute for its service, until the next pass. Until then its tool calls answer pack-endpoint-pending.

The Job has 1 vCPU and 1 GiB, and a 600-second timeout as a backstop. Cloud Scheduler starts it at * * * * *, in UTC, with an OAuth token of the orchestrator's account. Neither retries: the next minute's pass is the retry, and a pass that starts while another runs exits doing nothing. What the orchestrator's account may do is in The IAM it sets up.

Your pack services

The orchestrator makes each deployment's service, named kp-…, with the module's pack_* settings. Every one runs as the one pack account, $N-pack, so whatever one pack may read, each may.

• Size: 1 vCPU and 1 GiB, with a startup CPU boost.
• Scaling: up to pack_max_instances instances, 8 by default, each running pack_concurrency calls at once, 32 by default. Both are whole numbers from 1 to 1000.
• At zero when idle: a service scales to zero when it's idle, and its first call after a quiet spell waits for an instance to start.
• Timeout: pack_timeout, in whole seconds up to "3600s", "300s" by default. Keep it above the runtime's pack_call_timeout_ms, so the runtime reports a timeout before Cloud Run cuts the call.
• Network: internal ingress with network_mode = "direct", all ingress with "connector", with IAM as the guard (A new VPC, or yours). With "connector", each service reaches private ranges through the connector.
• Databases: the Cloud SQL instances in pack_cloud_sql_instances, at most 10, at /cloudsql. The pack account gets roles/cloudsql.client.
• Buckets: pack_bucket_readers, read with roles/storage.objectViewer, and pack_bucket_object_prefixes to narrow a bucket to some prefixes.

What it costs. A pack service bills only while it runs (Cloud Run pricing). The Job is billed per second of each pass.

How many. Cloud Run allows 1,000 services per region in a project, which a quota request can raise (Cloud Run quotas), and each deployment the runtime still serves has one. Unregister the old versions you don't need (What unregistering a version does).

Your pack's env

Terraform doesn't hold your pack's env. Each deployment's service gets it from the runtime: the names your pack declares, with the values you set through Kindgi, plain ones with kindgi env set (Declare the environment your code reads). pnpm exec kindgi env plan --env prod lists what your pack needs.

When a value changes, the orchestrator's next pass gives the running service its new env, with no deploy. While a name the pack requires has no value, a new deployment gets no service, and a running one keeps the values it was last given. A secret is the exception: once its name is no longer set as a secret, the service's copy of it in Secret Manager is deleted at once, without waiting for the missing names. kindgi deployments get <deployment-id> names what's missing. With secrets_backend = "none", a pack gets no secret stored in Kindgi: its plain values, and cloud secrets (Read a secret of yours).

Read a secret of yours

A pack's env can name a secret of yours in Secret Manager as a cloud secret, pinned to a version (the module turns this on: KINDGI_ENV_CLOUD_SECRETS=on). First list the secret in pack_secret_readers, by its id, not its path, with its project when it's in another project, and apply:

pack_secret_readers = [
  { secret = "acme-app-database-url", project = "acme-app" },
]

Excerpt

The pack account gets roles/secretmanager.secretAccessor on each secret alone, in the secret's own project, so whoever applies must be able to grant there. Every pack service runs as that one account, so each pack can read every secret listed. The plan refuses a path, a kp- id and a secret named twice.

Then set it. The grant comes first because, once it's set, the orchestrator's next pass gives the service a revision that reads it. Set it with a system key holding system:env-refs. With one tenant, the runtime refuses the API token here, so mint a key with it, as in step 1 of Turn on the pack orchestrator, with "scopes": ["system:env-refs"], and set with that key:

KEY=$(curl -sS -X POST "$URL/v1/system/keys" \
  -H @<(printf 'Authorization: Bearer %s\n' "$(gcloud secrets versions access latest --secret=$N-api-token)") \
  -H 'Content-Type: application/json' -H "Idempotency-Key: $(uuidgen)" \
  -d '{"scopes": ["system:env-refs"], "label": "cloud secrets"}' \
  | jq -j '.token // error(.error.message)') && [ -n "$KEY" ] \
  && KINDGI_API_TOKEN=$KEY pnpm exec kindgi env set DATABASE_URL \
       --tenant=<tenant id> --scope=tenant --env=prod --url "$URL" \
       --cloud-secret projects/acme-app/secrets/acme-app-database-url/versions/3
unset KEY

Behind Cloud Run IAM, add the ID token line after the curl line, as in step 1. KINDGI_API_TOKEN=$KEY gives the key to that one command, off the command line. The key stays valid until you revoke it. Once you've set what you need, revoke it: POST /v1/system/keys/{keyId}/revoke, with its id from GET /v1/system/keys (its label is cloud secrets). Serving many tenants, the API token holds the full system capability, kindgi:system, so set it with the API token in KINDGI_API_TOKEN (Serve many tenants).

A revision whose account can't read a secret it's given (say it was set before its grant) doesn't start, and the last ready one keeps serving. kindgi deployments get <deployment-id> shows the service held as pack-env-secret-unreadable. The orchestrator tries the same values again, each time as a new revision, 5, 10 and 20 minutes after each start that didn't take, so four starts at most, then leaves them held. Grant the read (list the secret in pack_secret_readers and apply), and the next start clears the hold. After the fourth, set the name again with --force (the same cloud secret: without --force, that's no change). That counts as new values, with four starts of their own.

Secret Manager logs a read of a secret's value only with its Data Access audit logs on. To record each read of a pack's secrets, turn on DATA_READ for Secret Manager in this project, and in each project pack_secret_readers names (Cloud Audit Logs: Data Access).

Call your app's Cloud Run services from a tool

When a tool calls one of your app's IAM-protected Cloud Run services, list it in pack_run_invokers, by its name, not its URL:

pack_run_invokers = [
  { project = "acme-app", location = "europe-west1", service = "orders-api" },
]

Excerpt

The pack account gets roles/run.invoker on each one, beside its other members; nothing else of the service changes. Every pack service runs as that account, so each deployment's tools may call it. The tool asks the metadata server for a Google ID token for the service's URL and sends it as Authorization: Bearer:

tools/call-service/index.ts

// acme.call-service: calls one of the app's IAM-protected Cloud Run services
// with a Google ID token for its URL from the metadata server, and reports
// what came back, as is.

import { defineTool } from '@kindgi/sdk/define';
import type { ToolId } from '@kindgi/sdk/types';
import { z } from 'zod';

const Input = z.object({ url: z.string().url() });

const Output = z.object({
  token: z.string(),
  status: z.number().optional(),
  body: z.string().optional(),
  headers: z.record(z.string(), z.string()).optional(),
  error: z.string().optional(),
});

const METADATA =
  'http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/identity';

const defined = defineTool({
  id: 'acme.call-service' as ToolId,
  description: "Call an app Cloud Run service with the pack's Google ID token; report the answer.",
  version: '0.1.0',
  input: Input,
  output: Output,
  effects: [{ kind: 'reads', resource: 'external:cloud-run' }],
  mutating: false,
  handler: async ({ url }) => {
    const audience = new URL(url).origin;
    const minted = await fetch(`${METADATA}?audience=${encodeURIComponent(audience)}`, {
      headers: { 'Metadata-Flavor': 'Google' },
    });
    if (!minted.ok) return { token: `refused ${minted.status}`, body: await minted.text() };
    const idToken = (await minted.text()).trim();
    try {
      const res = await fetch(url, { headers: { authorization: `Bearer ${idToken}` } });
      const headers: Record<string, string> = {};
      for (const name of ['content-type', 'www-authenticate', 'server', 'x-cloud-trace-context']) {
        const value = res.headers.get(name);
        if (value !== null) headers[name] = value;
      }
      return { token: 'minted', status: res.status, body: (await res.text()).slice(0, 2000), headers };
    } catch (cause) {
      return { token: 'minted', error: cause instanceof Error ? `${cause.name}: ${cause.message}` : String(cause) };
    }
  },
});

if (defined.kind === 'err') {
  throw new Error(`acme.call-service failed to compile: ${defined.error.message}`);
}

export default defined.value;

The call leaves through the pack service's own egress, so the service's ingress has to take it. A service with ingress all does, with IAM as the guard. A service with internal ingress refuses it with a 404, Google's "Page not found" page, not a 403, so the tool's error can look like a wrong URL. A call from Cloud Run to an internal service has to go through a VPC network, and the pack's calls to your services don't (Cloud Run: Restrict network endpoint ingress).

OpenFGA behind Cloud Run IAM

When OpenFGA runs as a Cloud Run service of its own, with IAM on, the runtime proves who it is to Cloud Run as well as to OpenFGA (runtime 0.1.8 or later). Give the runtime's service account roles/run.invoker on OpenFGA's service, run OpenFGA with a key and its playground off (Require a key for OpenFGA), and set:

openfga_api_url = "https://openfga-…a.run.app" # OpenFGA's own service URL
server_env = {
  KINDGI_OPENFGA_AUTH = "google-id-token"
}
server_secret_env = {
  KINDGI_OPENFGA_PRESHARED_KEY = { secret = "kindgi-openfga-key", version = "1" }
}

Excerpt

Each call then carries a Google ID token for that URL, from the runtime's own identity, in X-Serverless-Authorization, beside the key in Authorization. With both headers, Cloud Run checks only X-Serverless-Authorization, and passes the token on without its signature, so the key reaches OpenFGA (Cloud Run: Authenticating service-to-service). The URL is the token's audience, so use OpenFGA's service URL itself, over https. The startup line about OpenFGA's calls names the token too (KINDGI_OPENFGA_AUTH).

Keep the key's secret pinned to a version, as here: then change the key one deploy at a time.

Serve many tenants

By default (tenancy = "single") the server serves one tenant, seed_tenant_id's. With "multi", on runtime 0.1.8 or later, it serves every tenant created through POST /v1/system/tenants, and takes each request's tenant from its key or session. Either way each deployment is a Cloud Run service of its own, which the pack orchestrator makes (Turn on the pack orchestrator).

Every tenant's pack services run as the one pack account, $N-pack. So each tenant's pack code can read every kp- secret, other tenants' pack service tokens and secret env values among them, and every secret in pack_secret_readers. One installation is for tenants that trust one another's pack code. Give tenants that don't an installation each (Your tools' code).

tenancy         = "multi"
openfga_api_url = "https://openfga-…a.run.app"
# no seed_tenant_id or seed_user_id
server_env = {
  KINDGI_TENANT_HOST_ACCESS = "isolated"
}
server_secret_env = {
  KINDGI_OPENFGA_PRESHARED_KEY = { secret = "<a key OpenFGA accepts>", version = "1" }
}

Excerpt

• What the plan needs, and names when it's missing: openfga_api_url (without an authorization store no tenant would have an admin), KINDGI_OPENFGA_PRESHARED_KEY in server_secret_env (Require a key for OpenFGA), and KINDGI_TENANT_HOST_ACCESS = "isolated" in server_env. The server won't start without them.
• What the plan refuses: seed_tenant_id and seed_user_id.
• What the module sets: KINDGI_TENANCY=multi (the variable), and neither KINDGI_TENANT_ID nor KINDGI_SEED_USER_ID. pack_call_timeout_ms still caps each call.
• The API token is the operator's: it reaches only /v1/system/*, in no tenant. So step 5 and everything after it use a tenant's key instead:
  • A tenant: POST /v1/system/tenants with the API token. With firstAdmin, that person is its admin and holds every capability but secrets:reveal, to put on the keys they make (Who can do what). Without it, the answer carries the first admin's key, sent once. That key is a service account's, so the runs it starts count as unattended (Service accounts): for the work you start, add yourself as a person (Add a person) and use a key of your own.
  • Its image repository: the create's imagePrefix, or PUT /v1/system/tenants/{tenantId}/image-prefix, before its first deploy. Without it, a deploy is refused with 409 image-prefix-unset.
  • Its tools answer once the orchestrator has made the deployment's service, at its next pass. Until then, a run that calls one fails with pack-endpoint-pending: "The pack service of the deployment shipping … isn't ready yet."
• An existing deployment keeps its tenant, with its data, keys and people, as the first of many at the first "multi" boot. Before the switch:
  • OpenFGA first: if it has no openfga_api_url yet, add it (and the key) in a single-tenant apply. That boot makes the tenant's authorization store, with the seed user as its admin. Switching in the same apply leaves the tenant without one, and none can be made afterwards without naming its first admin.
  • A key of the tenant for anything that deploys or calls with the API token: after the switch, that token no longer reaches the tenant.
  • Then, in one apply: tenancy = "multi", without seed_tenant_id and seed_user_id, with the settings above.
• After an upgrade that adds a step per tenant, kindgi-runtime tenants repair --all has to run once: a server serving many tenants sets nothing up per tenant at boot. This module runs no such job. It also takes away access a tenant's record doesn't back (runtime 0.3.0 or later): it finishes a removal that stopped part way, and revokes a service account's admin, membership or project role that its grants don't give. And it takes away the access an older runtime gave 00000000-0000-0000-0000-000000000000, the id it named as the creator of what a key with no person behind it made; no person has that id. --dry-run shows what it would put back and take away, per tenant, and changes nothing.
• An earlier runtime ignores KINDGI_TENANCY. With no tenant id it would seed a new tenant at every start, so upgrade the runtime first.

5. Trust your key, and deploy

The runtime accepts only deploys signed by a key it trusts. Read its address and the first API token, trust your pack's key, then deploy. With tenancy = "multi", use a key of the tenant here and after, not the API token (Serve many tenants).

URL=$(terraform output -raw server_url)
export KINDGI_API_TOKEN=$(gcloud secrets versions access latest --secret=$N-api-token)
npx --yes @kindgi/cli@0.2 key trust acme-prod --url "$URL"

It prints the key the runtime now trusts, then says so:

{
  "keyId": "acme-prod",
  "tenantId": "722e23b8-bbb4-43dc-9a37-9640e369fa7d",
  "algorithm": "ed25519",
  "publicKey": "UCeKMLv5KIFRJo5exp/5BKzsPOKzdlmJYYuLKVYmEVo=",
  "createdAt": "2026-10-12T14:28:47.190Z"
}

  ✓ Trusted acme-prod (sha256:60e5a3c06154b3ee3e425037)
    The runtime now accepts deploys this key signs.

• gcloud secrets versions access reads the API token from step 3.
• acme-prod is your signing key's id, from ~/.kindgi/keys/.
• --url is the runtime's address. The commands send the API token, exported as KINDGI_API_TOKEN, which keeps it off the command line. kindgi deploy takes the address as --endpoint, and --env prod names the environment block to deploy.

pnpm exec kindgi deploy --env prod --endpoint "$URL"

It prints the deployment as JSON, then each step. The last steps:

…
  Registering deployment
    ✓ POST /v1/deployments  →  201 Created
      deploymentId:    b27ee9ec-…
      artifactVersion: …
      primitives:      3 tools, 1 guardrail, 1 agent, 2 flows
      activatedAt:     2026-10-04T22:23:24.370Z

  Deploy complete.
  Runs started from now use image sha256:bd7bfe4f7d9c8… (artifactVersion …).
  Runs already in flight keep their tool versions: each tool call goes to the newest deployment in the run's project that shipped the version it names.

Excerpt

The deployment's tools answer once the orchestrator has made its pack service, at its next pass, within about a minute. Until then a tool call answers pack-endpoint-pending. kindgi deployments get <deployment-id> shows whether its service is ready, and the command that sets a name its env is missing (kindgi deployments list --table lists the ids).

A deployment registered before the runtime routed per deployment, with the module's earlier single pack service, has no routes: its tool calls answer pack-route-missing. Deploy it again. The same image is enough, with --idempotency-key <new value> so the runtime doesn't answer it as it did the earlier deploy. The deploy answers with that same deployment and says its pack service is asked for, and kindgi deployments get <deployment-id> says when it's ready.

To deploy a client's pack into its own project, add --project <id or slug> (Deploy a client's pack into its project).

The runtime read your pack's image from Artifact Registry with its own token (KINDGI_IMAGE_REGISTRY_AUTH=google) to check it before registering it.

A deploy that's refused, for an untrusted key or a missing variable, says what to fix. Fix it and run the same command again.

6. Check it

Check the runtime answers, lists your pack's tools, and runs a flow:

curl "$URL/health"                                  # {"ok":true}
npx --yes @kindgi/cli@0.2 tools list --url "$URL"   # your pack's tools
npx --yes @kindgi/cli@0.2 runs start --flow=acme.greet-echo --input='{"name":"Ada"}' --url "$URL"

--flow names the flow to run, and --input is its input, as JSON.

Run them once the deployment's service is ready (step 5). In the verification run, made with the module's earlier single pack service, every run completed. A new instance of the runtime was ready in about 7 seconds, 8 with its first migrations, and the pack's service in about 5.

7. Turn on sign-in

Nobody can sign in to the console until you turn sign-in on. The API, the CLI and the SDKs take API tokens either way. Until then, the startup lines say so:

  ⚠ Console sign-in: nobody can sign in to the console. KINDGI_CONSOLE_TOKEN_SIGN_IN=on allows an API token; KINDGI_AUTH_SECRET_PATH turns on sign-in with identity providers.

The runtime's own settings go in two variables: server_env for plain values, and server_secret_env for Secret Manager secrets, read with the runtime's identity. You create each secret, and the runtime gets read access to exactly those (a secret in another project is granted there). The plan refuses a name the module sets itself (its own variables cover those, such as public_url below), KINDGI_DEV, and a secret given as a plain value: a name with SECRET in it, a preshared key, or the SMTP URL.

With an API token, which the console's sign-in page then takes:

server_env = {
  KINDGI_CONSOLE_TOKEN_SIGN_IN = "on"
}

Excerpt

With an emailed link, you need the runtime's sign-in secret, an SMTP server and public_url:

# The sign-in secret: 32 bytes, base64.
openssl rand 32 | base64 | gcloud secrets create $N-auth-secret --data-file=-
# The SMTP URL, password included: paste it; it never goes in a file.
read -rs SMTP_URL && printf '%s' "$SMTP_URL" | gcloud secrets create $N-smtp-url --data-file=- && unset SMTP_URL

public_url = "https://kindgi-server-abc123-pd.a.run.app" # terraform output -raw server_url
server_env = {
  KINDGI_CONSOLE_TOKEN_SIGN_IN = "on"
  KINDGI_AUTH_EMAIL_FROM       = "kindgi@acme.example"
}
server_secret_env = {
  KINDGI_AUTH_SECRET         = { secret = "kindgi-auth-secret", version = "1" }
  KINDGI_AUTH_EMAIL_SMTP_URL = { secret = "kindgi-smtp-url", version = "1" }
}

Excerpt

Pin each secret to a version, as here, rather than latest: a new version then reaches the runtime only when you change version.

• public_url (KINDGI_PUBLIC_URL) is the address people open the console at: terraform output -raw server_url after the first apply, so the emailed link comes with a second apply, or your own domain in front. Console sessions are then accepted from that address only. The plan refuses KINDGI_AUTH_SECRET without it, because the runtime wouldn't start. A tool that pauses hands other systems a link made from it too (On a server you run).

With Continue with Google, you need the sign-in secret and public_url, as for the emailed link, and an OAuth client of type Web application in the Google Cloud console (Google). Its authorized redirect URI is public_url followed by /auth/kindgi/social/callback/google:

https://kindgi-server-abc123-pd.a.run.app/auth/kindgi/social/callback/google

Store the client's secret, then give the runtime the client's ID and the secret:

# The Google client's secret: paste it; it never goes in a file.
read -rs GOOGLE_SECRET && printf '%s' "$GOOGLE_SECRET" | gcloud secrets create $N-google-client-secret --data-file=- && unset GOOGLE_SECRET

public_url = "https://kindgi-server-abc123-pd.a.run.app"
server_env = {
  KINDGI_AUTH_GOOGLE_CLIENT_ID = "<client id>"
}
server_secret_env = {
  KINDGI_AUTH_SECRET               = { secret = "kindgi-auth-secret", version = "1" }
  KINDGI_AUTH_GOOGLE_CLIENT_SECRET = { secret = "kindgi-google-client-secret", version = "1" }
}

Excerpt

• <client id> is the client's ID in the Google Cloud console, ending in .apps.googleusercontent.com.
• Microsoft and GitHub go the same way, with MICROSOFT or GITHUB in the names, and a redirect URI ending in microsoft or github (Continue with Google, Microsoft or GitHub). So do verified domains and Turnstile: KINDGI_AUTH_VERIFIED_DOMAINS and the Turnstile site key in server_env, and KINDGI_AUTH_TURNSTILE_SECRET in server_secret_env.
• Several ways in share the two maps: with the emailed link too, they hold both sets of settings.
• The module mounts no files, so use the value forms of the settings, such as KINDGI_AUTH_GOOGLE_CLIENT_SECRET, not their …_PATH forms.

Check it worked: after the apply, the new revision's startup lines say where it's reached, and which ways in the console has, instead of the warning. From a deployment with identity providers and the emailed link:

Kindgi API server listening on http://localhost:4000 (reached at https://kindgi-server-…a.run.app)
  Console sign-in: identity providers, or an API token (KINDGI_CONSOLE_TOKEN_SIGN_IN)
  …
  Pack services: one per deployment, at the endpoints recorded through the system API (1 allowed host pattern), each endpoint's token sealed under KINDGI_PACK_ENDPOINT_KMS_KEY's key

Excerpt

What each setting does, and the ways in: Turn on sign-in.

Use Gemini

The runtime can call Gemini on Vertex AI with its own service account, so there's no key to store. Set vertex_ai = true and apply: the module turns on the Vertex AI API and grants the runtime's service account roles/aiplatform.user. Then register the preset:

npx --yes @kindgi/cli@0.2 providers register --preset=gemini --project=<project> --models=gemini-3.8-flash --url "$URL"

{
  "providerId": "gemini"
}
✓ Registered gemini: gemini-3.8-flash (default)

• --preset=gemini registers Gemini on Vertex AI.
• <project> is your Google Cloud project's id.
• --models lists the models to offer. The first is the default.

Without the role, every model call fails. This one was captured with gemini-2.5-flash, and another model's call names that model:

Model call to gemini (gemini-2.5-flash) failed: {"error":{"code":403,"message":"Permission 'aiplatform.endpoints.predict' denied on resource '//aiplatform.googleapis.com/projects/<project>/locations/global/publishers/google/models/gemini-2.5-flash' (or it may not exist). …

Excerpt

A new grant can take a minute or two to apply.

Staging and production

Run staging and production as two deployments of the module, so a change or an upgrade reaches staging first. Each has its own:

• Folder: a copy of the module, at the same release, with its own var-file.
• State: its own prefix at terraform init (-backend-config=prefix=staging, say). Two deployments never share one.
• Variables: staging.tfvars in one folder and prod.tfvars in the other, each with its project_id, its name_prefix, and its kindgi_env: the env its tools' stored secrets resolve in, the one you name when you set them (--env=staging, say).
• Pack env: set on each deployment's runtime, through Kindgi (Your pack's env). kindgi env plan --env staging reads your pack config's staging environment (Per-environment values). Each environment in the pack config can also name its deployment's address (endpoint), so kindgi deploy --env staging deploys there.
• License key: a non-production key covers staging, as long as it serves no end users and processes no live business data (Two licenses).

Put the two in two Google Cloud projects. The module grants roles on the whole project: the runtime may invoke every Cloud Run service in it, the orchestrator may create and delete them, and the pack account may read every kp- secret in it. So run one installation of the module per project. Each project's resources, roles and quotas are then its own, and both deployments can keep the default name_prefix. Terraform takes the project from the var-file, but gcloud acts on the one it's set to, so set it to the deployment's before any gcloud command for it (gcloud config set project <project_id>).

Operate it

• Upgrade at least every 90 days. A preview release stops starting 90 days after it was released. Cloud Run starts new instances on its own, and after that day none comes up. The runtime warns from 30 days before, at startup and once a day, in a log record with jsonPayload.event = "kindgi.preview_expiry": set a log-based alert on it (Licensing).

• Upgrade: back up Cloud SQL, copy the new runtime image by digest, set server_image, and apply (Upgrade by hand has the steps). The new revision takes all the traffic. Migrations only go forward: never run two runtime versions on one database, and go back by restoring the backup. From a module copy older than secrets_aad_key_version, add it to prod.tfvars first, set to the version your server reads, normally 1 (gcloud secrets versions list $N-secrets-aad-key lists them). Without it, terraform plan stops and asks for it. From a module copy that set only Terraform's deletion protection, the next apply also turns on Google's in the instance, in place, while database_deletion_protection is on (the default). From a module copy that doesn't turn on Cloud Scheduler's API, the next apply turns it on (and, with secrets_backend = "none", Cloud KMS's). With a private-IP database (database_private_network), either change makes the module read the instance's CAs during the apply, so the plan shows the server's KINDGI_DATABASE_SERVER_CA as (known after apply): it's still the instance's CAs. If the plan says the instance must be replaced, stop: a replace deletes the database.

• Or upgrade with the module's upgrade.sh: a deployment of the module on runtime 0.1.8 or later, in any network_mode, can run it instead, to 0.4.0 or later. Before the @kindgi/sdk@0.3.0 tag it takes network_mode = "none" only. It copies the new image from registry.kindgi.com, so log in there first. It runs the upgrade checks against the database, then backs the database up, and changes the running deployment only when you type yes. Before it asks, it checks the plan: it stops if the plan replaces anything, or creates, deletes or changes anything but the new image and what the releases crossed change. So a var file left off the command, whose variables the plan would empty, stops it: give it one --var-file for each file your variables are in, since Terraform loads only terraform.tfvars and *.auto.tfvars (and their .json) on its own. yes applies exactly that plan, which it keeps next to the var-file's copy. If the new revision doesn't come up, it prints the way back rather than rolling back on its own. To see what it would do first, add --dry-run: it lists every change a real run would make, in order, and shows Terraform's plan for the new image, but changes nothing and never asks for yes. It doesn't run the upgrade checks against the database, since they run as jobs in your project. Use the upgrade.sh as of the @kindgi/sdk@<version> tag of the release you're upgrading to, or, before that release is out, its newest @kindgi/sdk@<version>-rc.N tag: it knows the steps up to its own release, and refuses a later --to. The module needs runtime 0.4.0 or later, so its upgrade.sh refuses a --to below that, and names the tag whose script goes there. With an earlier --to it takes, it still plans its own module, whose changes past the target's release it lists and allows, and it says so. With the one pack service, it makes the switch to a service per deployment, and prints the steps that finish it after the apply (From the one pack service). A server-only release, such as 0.2.0.1, is a server fix for 0.2.0 with no @kindgi/sdk@ tag of its own: use the upgrade.sh as of the @kindgi/sdk@0.2.0 tag, with --to 0.2.0.1. The module's README has the rest, under Upgrading, and ./upgrade.sh --help lists its options.

• Backups: Cloud SQL backs the database up daily, with point-in-time recovery. On the module's edition (ENTERPRISE) it keeps 7 backups and 7 days of transaction logs by default, in the multi-region nearest the instance (Google: Cloud SQL backup options). To keep more, or choose where they're stored, set database_backup_retention, database_point_in_time_days (at most 7 on ENTERPRISE, and at most as many days as backups kept) and database_backup_location. A restore reaches any second within the logs' days, or one of the kept backups.

  • Where the backups are kept: the nearest multi-region can be outside the instance's region and country. When you promise where backups are kept, set database_backup_location to a region (northamerica-northeast2, say) or a multi-region (us, eu, asia); a zone is refused at plan. Point-in-time recovery's transaction logs stay in the instance's own location (Google: transaction log retention).
  • Setting it on a running deployment changes the instance in place. The backups taken before stay where they were (Google: custom backup locations).
  • On a host or a restored instance: these set the module's own instance only. With database_host_instance they're refused at plan: the host's backups are the app's, set where that instance is managed. An instance database_instance names keeps its own.

• Restore Cloud SQL: a point-in-time recovery always makes a new instance, and a backup can go into one too (restored into the serving instance, it overwrites everything on it). database_instance moves the server onto the new instance: the instance's name, and a secret of yours holding the server's URL to it. The module's own instance stays as it is, and doesn't get the erasures made later: empty it once the new one is checked (Erasures and backups). The module's README has the steps, under Serving from a restored instance:

  • the new instance's deletion protection, which the module doesn't manage there: turn it on before it serves;
  • the new instance's URL, and the server's read access to it;
  • the erasure replay before it serves (Erasures and backups);
  • the switch, and the way back.

• Rotate a secret: add a version, then roll a new revision of the runtime's service (gcloud run services update $N-server --update-labels=rotated=$(date +%s)). The orchestrator's key is pinned: mint a new one as in Turn on the pack orchestrator, add it as the secret's next version, set orchestrator_key_version to it and apply. Once a Job execution after the apply has succeeded (gcloud run jobs executions list --job=$N-pack-orchestrator --region=<region> --limit=1), revoke the old one, POST /v1/system/keys/{keyId}/revoke, with the old key's id from GET /v1/system/keys (Serve many tenants).

• A pack service's logs: each deployment's service logs under its own kp-… name, and the orchestrator's passes under the Job, $N-pack-orchestrator.

• The AAD key is never rotated. Every stored secret is bound to the version the server reads, so a new version is a key change that needs every stored secret re-encrypted first. The pin keeps a version added by mistake away from the server.

• Client addresses: the module trusts one proxy, Cloud Run's front end, which adds the caller to X-Forwarded-For. That's trusted_proxies = "1", the runtime's KINDGI_TRUSTED_PROXIES, so rate limits and sign-in records see the caller. Behind an external Application Load Balancer, set "2": it adds the client and then its own address (Google: X-Forwarded-For header).

• Database timeouts (they need runtime 0.1.9 or later): the server's connections carry their own, 60 s a statement, 30 s waiting for a lock, and 30 s idle in a transaction, and a query waits at most 10 s for one of the server's pooled connections. KINDGI_DB_STATEMENT_TIMEOUT_MS, KINDGI_DB_LOCK_TIMEOUT_MS, KINDGI_DB_IDLE_IN_TRANSACTION_TIMEOUT_MS and KINDGI_DB_POOL_WAIT_TIMEOUT_MS in server_env change them; 0 turns one off. A GET or HEAD the statement or lock timeout or the pool wait ends answers 503 database-busy with Retry-After: 5 (under /auth/, a browser signing in is sent back to the sign-in page instead), any other request 500, and the log has a db warning naming the setting, its value and its variable. The instance itself ends any other session left idle in a transaction for 10 minutes (database_idle_in_transaction_timeout_ms, 0 for off). An instance from before that variable gets the flag at the next apply, in place: Cloud SQL lists it as needing no restart (Cloud SQL: configure database flags).

• Erasures, after a restore: a memory erasure keeps a keyed hash of whom it erased, so it can be replayed after you restore a backup. The key goes in Secret Manager, named in server_secret_env:

  openssl rand 32 | base64 | gcloud secrets create $N-erasure-ledger-key --data-file=-

  server_secret_env = {
    KINDGI_ERASURE_LEDGER_KEY = { secret = "kindgi-erasure-ledger-key", version = "1" }
  }

  Excerpt

  The startup lines then say:

    Erasures: on; the ledger is replayable after a backup restore (key from KINDGI_ERASURE_LEDGER_KEY)

  Without it, they say erasures aren't replayable. Keep the key: losing it means losing replay (Erasures and backups).

• Logs: Cloud Logging, per service. The runtime logs JSON there, one record per line, and Cloud Logging reads each record's severity. Filter by jsonPayload.traceId to follow one request or run. The startup lines are the lines of its boot record, as in The startup log. See Logs.

Upgrade by hand

upgrade.sh runs these steps for you. Upgrade by hand instead if you'd rather, or with network_mode direct or connector and an upgrade.sh from before the @kindgi/sdk@0.3.0 tag, which takes "none" only. Upgrade staging first (Staging and production). Run the steps in the module's folder, as the identity that deploys the module, with gcloud set to this deployment's project, the project_id in its var-file:

gcloud config set project <project_id>

Terraform acts on the var-file's project, and gcloud on the one it's set to. Set to another deployment's project with the same name_prefix, the backup in step 4 would back that one up, and the apply would then upgrade this one with no backup. N is your name_prefix, and REPO the repository from 2. The images into Artifact Registry.

1. Read the upgrade steps of each release you're upgrading across, in its release notes, and note the new release's digest: docker pull registry.kindgi.com/kindgi/runtime:<version> prints it (Pull the runtime image).

2. Copy the new runtime image into Artifact Registry by digest, every platform included, as in 2. The images into Artifact Registry, from registry.kindgi.com (it has 0.2.0 and later):

   docker buildx imagetools create --tag "$REPO/runtime:<version>" \
     registry.kindgi.com/kindgi/runtime:<version>@sha256:<digest>

3. Run the new version's read-only checks against the database (Checks you can run before upgrading), as a Cloud Run job that reaches it the way the server does. With direct and a private-IP database:

   SA=$(terraform output -json service_accounts | jq -r .server)
   gcloud run jobs create $N-upgrade-check --region=<region> \
     --image="$REPO/runtime@sha256:<new digest>" --service-account="$SA" \
     --set-secrets=KINDGI_DATABASE_URL=$N-database-url:latest \
     --network=$N --subnet=$N-run --vpc-egress=all-traffic \
     --args=check,provider-keys --max-retries=0
   gcloud run jobs execute $N-upgrade-check --region=<region> --wait

   • Other shapes: with connector and a private-IP database, use --vpc-connector=<your connector> --vpc-egress=private-ranges-only in place of the three network flags. With a database on a public IP, add --set-cloudsql-instances=<its connection name>; with connector, the job then needs no network flags at all.
   • Serving from a restored instance (database_instance set): the server's URL is in that setting's url_secret, not $N-database-url. Name that secret in --set-secrets, and that instance's connection name in --set-cloudsql-instances.
   • For each other check the release notes name, change the job's --args with gcloud run jobs update, and run it again.
   • A check that finds something exits 1, and one that can't run exits 2: either way its run fails, and its logs say why. Delete the job when you're done (gcloud run jobs delete).
   • In private-IP mode the server also checks that the database's certificate chains to the instance's CAs (KINDGI_DATABASE_SERVER_CA). The job doesn't: with the URL's sslmode=require alone, it encrypts the connection and checks no certificate. It only reads, over the private network.

4. Back up the database, just before you apply:

   • The module's own instance ($N), which holds only Kindgi's database, or the one database_instance names: an on-demand backup.

     gcloud sql backups create --instance=$N --description="before <version>"

   • With database_host_instance, the instance's backups are the app's: export Kindgi's database instead, as upgrade.sh does. The instance's own service account writes the export, so give it write on the bucket first:

     SQL_SA=$(gcloud sql instances describe <instance> --format='value(serviceAccountEmailAddress)')
     gcloud storage buckets add-iam-policy-binding gs://<bucket> \
       --member="serviceAccount:$SQL_SA" --role=roles/storage.objectAdmin
     gcloud sql export sql <instance> gs://<bucket>/<file>.sql.gz --database=<database_name>

     A new grant can take a few minutes to take effect. Until it does, the export is refused with HTTP 412 and "the required permissions for the bucket", or with HTTP 403, "failed to initiate resumable upload" and "storage.objects.create": wait a minute and run the export again. A 403 without "storage.objects.create", such as one from an organization policy or VPC Service Controls, isn't the grant's delay, and waiting won't fix it.

   Writes made after the backup aren't in it.

5. Set the new image: server_image in prod.tfvars, to $REPO/runtime@sha256:<new digest>. Keep a copy of the file as it was: it's your way back. With the one pack service, read From the one pack service first.

6. Plan, and save the plan:

   (umask 077 && terraform plan -var-file=prod.tfvars -out=upgrade.tfplan)

   Terraform also reads every *.auto.tfvars.json in the folder. Read the plan: it should change the server's image, the pack orchestrator Job's too once it's made, and what the release notes say. A plan that removes some of the server's own env (server_env, server_secret_env) was made without the file it's in.

   The plan holds your variables' values, secret ones too: umask 077 keeps it readable by you alone, and you delete it once it's applied.

7. Apply exactly that plan:

   terraform apply upgrade.tfplan
   rm upgrade.tfplan

   A saved plan applies as you read it, with the variables it was made with, so it takes no -var-file. If the state changed since, Terraform refuses it as stale: plan again. The new revision takes all the traffic once it's ready.

8. Check it, as in 6. Check it.

If it doesn't come up, go back. Nothing rolls back on its own, and migrations only go forward, so never point the old version at the migrated database:

1. First, export the erasure ledger from the server serving now (Erasures and backups). It holds every erasure so far, those made after the backup too. If no server answers, the backup's own ledger is all there is.

2. Save the plan that goes back, before you bring the database back. Put server_image back from the copy of prod.tfvars you kept, then plan, and read it. After the switch from the one pack service, put the earlier module back first (From the one pack service):

   (umask 077 && terraform plan -var-file=prod.tfvars -out=back.tfplan)

   Like the upgrade's plan, this one holds your secret values too.

   The server runs its migrations each time one of its instances starts. So apply this plan as soon as the database is back: an instance of the new version that starts in between, on a restart or a scale-up, would migrate the database forward again.

3. Bring the database back, then apply that plan at once:

   • From a backup: restore it into the instance it came from. That overwrites everything on the instance, which is what going back needs:

     gcloud sql backups list --instance=$N
     gcloud sql backups restore <backup id> --restore-instance=$N

     The new version serves until the apply, and a restore takes the instance down for minutes. If the new version's revision started an instance after the restore finished (its logs show it), restore once more after the apply: by then only the old revision serves.

     With a database on a public IP, you can restore into a new instance instead, and move the server onto it, as Restore Cloud SQL under Operate it says: set database_instance along with the old images, and plan again for the apply. The server then moves and goes back in one revision, so the new version never serves from the restored instance. The module's instance keeps the migrated database: empty it once the restored one is checked (Erasures and backups). Private-IP mode can't serve from another instance.

   • From an export: make a fresh database on the instance, import the export into it as kindgi, and add a version of the server's database URL secret that names the fresh database, with the password set as in 3. The secrets, never in a command's arguments. Add that version last, right before the apply. Don't change database_name instead: the module would drop the migrated database, then fail to create the fresh one. The migrated kindgi database stays on the instance: empty it once the fresh one is checked (Erasures and backups).

     gcloud sql databases create <fresh> --instance=<instance>
     gcloud sql import sql <instance> gs://<bucket>/<file>.sql.gz \
       --database=<fresh> --user=kindgi

   Then apply the saved plan:

   terraform apply back.tfplan
   rm back.tfplan

   If Terraform refuses it as stale, plan again and apply at once.

4. Replay the erasures before anyone uses it (Erasures and backups). A replay matches only when the server has its ledger key (Erasures, after a restore under Operate it). With secrets_backend = "postgres", also run the old version's check stored-secrets, as a job like the checks in the upgrade's step 3, with the server's secrets settings as well as its database URL.

From the one pack service

A deployment made with an earlier copy of the module runs its packs one of two ways: one pack service for all its deployments, set by pack_image, pack_min_instances, pack_env and pack_secret_env, or, with tenancy = "multi", a service per deployment that your own orchestrator makes. This module's pack orchestrator makes each deployment's service (Turn on the pack orchestrator), and the module needs runtime 0.4.0 or later. It has none of those four variables: Terraform only warns about them in a var file. upgrade.sh makes this switch, and after the apply prints the steps that finish it, with your names in them and never a value. By hand, along with steps 5 to 8 above:

• Before the plan: take out of server_env and server_secret_env what the module sets itself: KINDGI_PACK_ROUTING, KINDGI_PACK_ENDPOINT_HOSTS, KINDGI_PACK_ENDPOINT_KMS_KEY and KINDGI_ENV_CLOUD_SECRETS. Its plan refuses them there. Leave the four pack variables in the var file until the second apply (step 2 below). With "multi", stop your own orchestrator.
• The plan, with the one pack service, deletes it, its token's secret and their grants. It makes the orchestrator's account, its grants and its key's secret, the server's right to invoke the project's services, and, with secrets_backend = "none", the KMS key the pack services' tokens are sealed under. In the server's env, the module's routing settings take the place of KINDGI_PACK_SERVICE_URL, KINDGI_PACK_SERVICE_TOKEN and KINDGI_PACK_SERVICE_AUTH (with "multi", of the ones you took out of server_env).
• With the one pack service, from the apply until each pack is deployed again, calls to a deployed pack's tools are refused: pack-route-missing, then, for about a minute, pack-endpoint-pending. Pick a quiet hour. With "multi", the services your orchestrator made keep serving until each tenant deploys again (step 5 below).

After the apply:

1. Mint the orchestrator's key into $N-orchestrator-key, as step 1 of Turn on the pack orchestrator says.
2. Set orchestrator_key_version to the version step 1 added, take the four pack variables out of the var file, and add each secret pack_secret_env names to pack_secret_readers (Read a secret of yours). Then plan, read the plan, and apply it: it makes the Job and its schedule, and the pack account's grants on those secrets.
3. Set the pack's env in Kindgi (Your pack's env), from the copy of the var file you kept: each pack_env value with kindgi env set, and each pack_secret_env entry as a cloud secret, at its version number. At the tenant's scope each deployment gets it, as the one pack service did.
4. Deploy each pack again, with the same image and a new --idempotency-key (5. Trust your key, and deploy). A pack service scales to zero when it's idle, whatever pack_min_instances was.
5. With "multi", each tenant deploys its packs again, with a key of the tenant. An endpoint your orchestrator recorded stays as it is, and its calls keep reaching your service while its host matches *-<project number>.<region>.run.app. Each old deployment is then retired: once GET /v1/system/deployments?endpoint=retire no longer lists one, delete the service your orchestrator made for it, its token and its secrets.

To go back after the switch, put the earlier module back before step 2 of going back, above: its .tf files as of the @kindgi/sdk@<version> tag of the release the deployment ran, in place of this module's (keep .terraform/, the state and your var files), and the var file you kept. Then, by the deployment's shape:

• With secrets_backend = "none", the earlier module has no KMS key, and a key can't be destroyed: take it out of the state. It stays in the project, unused. Remove each of these that terraform state list lists:

  terraform state rm google_kms_crypto_key_iam_member.server_wraps \
    google_kms_crypto_key_iam_member.server_reads_key \
    google_kms_crypto_key.secrets google_kms_key_ring.kindgi

• With the one pack service, if terraform state list lists no google_secret_manager_secret.shared, the apply took its token's secret away. Make it again, with a new value, and give it to the module, or the pack service and the server can't start:

  gcloud secrets create $N-pack-service-token --replication-policy=user-managed --locations=<region>
  openssl rand -hex 32 | tr -d '\n' | gcloud secrets versions add $N-pack-service-token --data-file=-
  terraform import -var-file=prod.tfvars 'google_secret_manager_secret.shared["pack_service_token"]' \
    projects/<project_id>/secrets/$N-pack-service-token

• With "multi", give server_env back KINDGI_PACK_ROUTING ("per-deployment") and KINDGI_PACK_ENDPOINT_HOSTS, if the copy you kept doesn't have them, and start your own orchestrator again.

That plan takes away the orchestrator's Job, schedule, account, roles and key secret, and makes the one pack service again: from its apply until the service is up, calls to the pack's tools are refused again. The kp- services and secrets the orchestrator made aren't in the state. Nothing calls them after the way back, and they stay until you delete them.

Tear it down

Cloud SQL can't be deleted while database_deletion_protection is on (the default). It turns on Terraform's deletion protection and Google's, which refuses a delete from the console, gcloud or the Cloud SQL API as well. Set it to false and apply first: the apply turns both off. The KMS key ring and key outlive terraform destroy: Google Cloud never deletes them. Take them out of Terraform's state, destroy the rest, then schedule the key's versions for destruction:

terraform apply -var-file=prod.tfvars -var=database_deletion_protection=false
terraform state rm 'google_kms_crypto_key.secrets' 'google_kms_key_ring.kindgi'
terraform destroy -var-file=prod.tfvars
gcloud kms keys versions destroy 1 --key=$N-secrets --keyring=$N --location=<region>

If the destroy stops at the subnet (is already being used by …/addresses/serverless-ipv4-cloudrun-…), Cloud Run hasn't released its addresses: run it again later.

The pack services and their kp- secrets are the orchestrator's, not in Terraform's state, so terraform destroy leaves them. Once it has run, so no pass makes them again, list them:

gcloud run services list --region=<region> --filter='metadata.name ~ ^kp-' --format='value(metadata.name)'
gcloud secrets list --filter='name ~ /secrets/kp-' --format='value(name)'

Then delete each, with gcloud run services delete <name> --region=<region> and gcloud secrets delete <name>.

Next

• Cloud Run module reference: the network, the secrets backend, how the runtime calls your pack services, the IAM it sets up, and its limits.
• Operate a self-hosted runtime: health, backups, upgrades and rotating keys.
• Turn on sign-in: every way in, and what each setting does.