Repository navigation
docs(self-hosting): close GKE guide gaps from infra #495 - #325
Conversation
- Step 4: leave desktop_feed_bucket_name out during the install; the bucket without a signing key makes relay-control exit. Recovery in Troubleshooting. - Step 7: the services, psql and chart pins belong to agent-relay-2026.11.16; how to read them for another release. - Step 14: the Ingress takes 15 to 20 minutes; a one-off BackendConfig translation warning is harmless; 502 on closed paths is intended. - Step 15: first-admin.sh gains optional API_HOST and PASSWORD_FILE (copied from infra at the #495 head, keeping the website's own line 2). - Regenerate SHA256SUMS and the downloads table. Co-Authored-By: Claude <noreply@anthropic.com>
Composal Verify · PR #325Warning This request is merged; previous verification results remain in the history. No high-confidence scenario matches were found; no preview or browser run is needed Diff assessment: Updates browser-rendered self-hosting documentation, including GKE installation guidance, troubleshooting sections, and download checksums. Also updates the publicly downloadable first-admin.sh script with API_HOST and PASSWORD_FILE options. Why no scenarios were selectedNo saved scenario matched this change. Recent verification history
|
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
|
Preview deployed!
This is a Cloudflare Workers preview version of this PR's build. |
Mirrors AgentWorkforce/infra#495 into the website's GKE guide. Merge after infra#495: the served
first-admin.shis a copy of infra's at the #495 head (1e4692a2), with the website's own comment line 2 kept.What changed
install-gke.mdstep 4 (leavedesktop_feed_bucket_nameout during the install, the error it causes); feed section item 1 (don't rerunhelm upgradeuntil item 3); new Troubleshooting section relay-control exits: signer and storage must be set together with thejq 'del(.["relay-control"].extraEnv)'recoverySERVICES_IMAGE,PSQL_IMAGE, chart.tgzagent-relay-2026.11.16(chart 0.7.54); how to read them from another release'srelease/release-manifest.json, andinfra/releases/<tag>/pins.jsonfor the services imageTranslation failed ... no BackendConfigwarningfirst-admin.shAPI_HOSTandPASSWORD_FILELeft out, on purpose
helm dependency buildfor installing from a checkout: the website guide installs only the released.tgz(step 11 and 13 userelease/agent-relay-0.7.54.tgz); it never tells a reader to install the chart from theinfracheckout. The checkout half of #495's pins note is left out for the same reason.desktop_feed_has_signing_keys: exists only on inframainafter #495, not inagent-relay-2026.11.16, which this guide pins. The Troubleshooting entry says the pinned Terraform has no such setting and gives thejqrecovery instead. Add the variable when the guide moves to a release that has it.PASSWORD_FILE, delete that file"): the website teardown page doesn't cover the first-admin secret today, so there is no matching line.Checks
node scripts/selfhost-files.mjs write, thencheck:selfhost-files: up to date(exit 0)npm test: 637 + 319 passed;npm run lint: exit 0;npm run typecheck: exit 0shellcheckandbash -nonfirst-admin.sh: cleanscripts/selfhost/tests/gcp-first-admin-test.sh(at the #495 head) run against this repo's copy: all passedjqline from step 7 run against theagent-relay-2026.11.16release manifest: prints the same digests the guide pins🤖 Generated with Claude Code
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.Summary by cubic
Syncs the GKE self-hosting guide and its
first-admin.shscript with the fixes from infra#495, so the install docs no longer steer readers into failures.desktop_feed_bucket_nameunset during install; enabling storage without the signing key makes relay-control exit repeatedly. Adds a Troubleshooting entry with ajqrecovery, and warns not to rerunhelm upgradeuntil the key exists.SERVICES_IMAGE,PSQL_IMAGE, andagent-relay-0.7.54.tgzbelong to releaseagent-relay-2026.11.16and how to read the correct ones for a different release.Translation failed ... no BackendConfigwarning is harmless, and that 502 on closed paths is expected when no Cloud Armor policy is set.first-admin.sh: adds optionalAPI_HOSTandPASSWORD_FILE; the password can now be kept in a local file instead of Secret Manager. SHA256SUMS and the downloads table updated.Written for commit d19afe8. Summary will update on new commits.