Onboard otel-a2a-relay-deploy repo to the fleet (remotes, hooks, registry, CI secrets, lockdown) #41

New issue

Closed

opened 2026-06-02 09:26:22 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-06-02 09:26:22 +00:00

Owner

New repo otel-a2a-relay-deploy was scaffolded locally (split out of otel-a2a-relay, tracking otel-a2a-relay#25). It holds the relay's Dockerfile, Helm chart, and homelab manifests, and consumes the otel-a2a-relay-core package. The chart is validated locally (helm lint + helm template clean via coily). It needs fleet onboarding:

Create the canonical Forgejo repo coilyco-flight-deck/otel-a2a-relay-deploy and the PR-gated GitHub mirror; add origin with the fan-out pushurl; push the bootstrap commit.
Apply the managed agentic-os pre-commit hook block (documentation-layout, catalog-trifecta, check-coily-yaml, coily-trailer, closes-issue) - the repo currently ships a minimal standalone .pre-commit-config.yaml.
Register in the repo registry + catalog graph (catalog block is in .coily/coily.yaml, dependsOn otel-a2a-relay).
Set the GitHub repo secrets the Docker publish workflow needs: DOCKERHUB_USERNAME, DOCKERHUB_TOKEN.
Run coily setup / lockdown to write .claude/ and finalize the ward/coily bridge (mirrors otel-a2a-relay#30: install the ward binary, repoint hooks + catalog to .ward/ward.yaml, drop the .coily bridge).
Mint the tailnet authkey for the relay: add o2r to the infra terraform/tailscale/ services.yaml and apply, landing /coilysiren/o2r/ts-authkey in SSM. Seed /coilysiren/o2r/peers (SecureString, empty to start).

Then: build/push the image, helm install per deploy/README.md, and confirm a real cross-host A2A session lands as traces in SigNoz (the #25 acceptance).

Migrated from coilysiren/inbox#24.

New repo `otel-a2a-relay-deploy` was scaffolded locally (split out of otel-a2a-relay, tracking otel-a2a-relay#25). It holds the relay's Dockerfile, Helm chart, and homelab manifests, and consumes the `otel-a2a-relay-core` package. The chart is validated locally (`helm lint` + `helm template` clean via coily). It needs fleet onboarding: - Create the canonical Forgejo repo `coilyco-flight-deck/otel-a2a-relay-deploy` and the PR-gated GitHub mirror; add `origin` with the fan-out pushurl; push the bootstrap commit. - Apply the managed agentic-os pre-commit hook block (documentation-layout, catalog-trifecta, check-coily-yaml, coily-trailer, closes-issue) - the repo currently ships a minimal standalone `.pre-commit-config.yaml`. - Register in the repo registry + catalog graph (catalog block is in `.coily/coily.yaml`, dependsOn otel-a2a-relay). - Set the GitHub repo secrets the Docker publish workflow needs: `DOCKERHUB_USERNAME`, `DOCKERHUB_TOKEN`. - Run `coily setup` / lockdown to write `.claude/` and finalize the ward/coily bridge (mirrors otel-a2a-relay#30: install the ward binary, repoint hooks + catalog to `.ward/ward.yaml`, drop the `.coily` bridge). - Mint the tailnet authkey for the relay: add `o2r` to the infra `terraform/tailscale/` services.yaml and apply, landing `/coilysiren/o2r/ts-authkey` in SSM. Seed `/coilysiren/o2r/peers` (SecureString, empty to start). Then: build/push the image, `helm install` per `deploy/README.md`, and confirm a real cross-host A2A session lands as traces in SigNoz (the #25 acceptance). --- _Migrated from coilysiren/inbox#24._

coilysiren referenced this issue

2026-06-02 09:29:10 +00:00

Arch bump: package the full o2r system as a Helm chart #25

coilysiren added the

label

2026-06-04 08:16:41 +00:00

coilysiren commented

2026-06-17 08:23:48 +00:00

Author

Owner

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.

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`.

coilysiren

2026-06-17 08:23:48 +00:00