Split rationale: kua-deploy used to be a service in coder-core/services/kua-services/docker-compose.yml, which meant every release-app coder-core rebuilt+force-recreated kua-deploy as a side-effect. The recreate-self path is structurally racy (the compose-up process is killed mid-flight when its own container stops), causing silent false-success deploys. This split makes kua-deploy its own deploy unit (own repo, own compose project, own release-app entry), so coder-core releases no longer touch it. Phase A (transient-container recreateService pattern) will follow to make deliberate kua-deploy self-updates also reliable. Handoff: v2-deploy-coordination -> kua-deploy-split (.sessions.md 2026-05-21 21:35). |
||
|---|---|---|
| Dockerfile | ||
| NOTES-image-digest-pinning.md | ||
| README.md | ||
| docker-compose.yml | ||
| kua.json | ||
| package-lock.json | ||
| package.json | ||
| server.js | ||
README.md
kua-deploy
Authoritative deploy orchestrator for the Kua infrastructure fleet. Receives release triggers (admin API and Forgejo webhooks), runs git-pull → migration gate → docker build → recreate → SHA-verify on managed apps.
Split out of coder-core/services/kua-deploy/ on 2026-05-21 to break the self-rebuild loop that ran every coder-core release through this service as a side-effect.
Layout
server.js— Fastify app exposing/api/v1/apps/:app/deploy,/progress,/runtime-status,/webhook/forgejo.Dockerfile— node:22-alpine + docker-cli + ssh + git + kua-vault binary (mounted at runtime).docker-compose.yml— single-service compose project. Joinskua-services+production_proxynetworks.kua.json— release-app manifest (mode: direct,server: bruno).NOTES-image-digest-pinning.md— design notes for deferred prevention #4.
Registry
deploy-registry.json lives in coder-core/services/kua-deploy/deploy-registry.json and is bind-mounted in at /app/deploy-registry.json. This is a transitional arrangement; a future change can migrate the registry into this repo.
Deploying kua-deploy
Via release-app:
release-app kua-deploy
Which goes through kua-deploy's own admin POST /api/v1/apps/kua-deploy/deploy and uses the transient-container recreate pattern (Phase A) so the service can replace its own running container without false-success.
See also
services/kua-deploy/NOTES-image-digest-pinning.mdin this repoinfra-docs/docs/04-operations/deploy-listener.mdin coder-core (current-state callout + deploy_mode reference)