Deploy channels: thin server + Postgres, behind chart channels.enabled #29
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/otel-a2a-relay#29
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up from the Helm chart work (#25). The chart shipped relay-only in v1.
otel-a2a-relay-channelsis a router-only library: no standalone server, nocreate_app, no__main__. Its only consumer is thebackendrepo, which injects the pool/auth. So deploying channels is not "package an existing service" - it needs new application code.To chart channels:
o2r-channels-serverentrypoint (FastAPI app that mountsmake_router(...), bootstraps the schema, builds an asyncpg pool fromDATABASE_URL).chart/behind achannels.enabledflag (values keys are already namespaced so this is non-breaking).postgres:17StatefulSet (forgejo's homelab pattern) vs an external DB viaDATABASE_URLfrom a Secret.deploy/namespace.yml.Acceptance: a deployed channels endpoint coordinating real cross-host agents, events landing as OTel spans in SigNoz alongside the A2A traces.
Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag:
burndown-2026-06.