coilyco-flight-deck/otel-a2a-relay
Archived
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

o2r packaging: migrate deploy/services chart in-tree; strip coilyco-bridge/deploy to pure GitOps #51

New issue
Closed
opened 2026-06-02 23:11:46 +00:00 by coilysiren · 1 comment
coilysiren commented 2026-06-02 23:11:46 +00:00
Owner
Copy link

Part of #45. Reframed (Kai, 2026-06-02): otel-a2a-relay-deploy was already renamed/reframed into coilyco-bridge/deploy, a general-purpose deploy monorepo that currently holds the o2r Dockerfile + Helm chart + manifests. The decision is to migrate the in-tree-able bits out and make deploy pure GitOps.

Scope

  • Move deploy/services/otel-a2a-relay/Dockerfile and deploy/services/otel-a2a-relay/chart/ into otel-a2a-relay in-tree (relay chart -> core/chart/, Dockerfile -> core/). Preserve the existing chart templates (deployment, service, ingress, hpa, pdb, networkpolicy, secret, serviceaccount, values.schema.json, tests) - this is a move + adapt, not a rewrite.
  • Leave in deploy: the ArgoCD Application(s) and per-env values (deploy/services/otel-a2a-relay/deploy/ values, tailscale-service as the exposure plugin's values), now pointing at the OCI-published chart instead of a local path.
  • Reverse the README philosophy in both repos: deploy/README.md says "service repo stays unaware of how it is deployed" - update to "charts live with code, deploy holds GitOps state + values."
  • Rewrite otel-a2a-relay README.md ## Deploy to the in-tree + OCI + ArgoCD model.
  • Reconcile closed #25 (note #45 supersedes).

Acceptance

  • No chart templates or Dockerfiles remain under deploy/services/*/; only ArgoCD apps + values.
  • o2r README ## Deploy and deploy README both describe the in-tree-chart / OCI / ArgoCD model with no contradictions.
Part of #45. **Reframed** (Kai, 2026-06-02): `otel-a2a-relay-deploy` was already renamed/reframed into **`coilyco-bridge/deploy`**, a general-purpose deploy monorepo that currently holds the o2r Dockerfile + Helm chart + manifests. The decision is to **migrate the in-tree-able bits out and make `deploy` pure GitOps.** ### Scope - **Move** `deploy/services/otel-a2a-relay/Dockerfile` and `deploy/services/otel-a2a-relay/chart/` **into `otel-a2a-relay` in-tree** (relay chart -> `core/chart/`, Dockerfile -> `core/`). Preserve the existing chart templates (deployment, service, ingress, hpa, pdb, networkpolicy, secret, serviceaccount, values.schema.json, tests) - this is a move + adapt, not a rewrite. - **Leave in `deploy`:** the ArgoCD `Application`(s) and per-env values (`deploy/services/otel-a2a-relay/deploy/` values, tailscale-service as the exposure plugin's values), now pointing at the **OCI-published** chart instead of a local path. - **Reverse the README philosophy** in both repos: `deploy/README.md` says "service repo stays unaware of how it is deployed" - update to "charts live with code, deploy holds GitOps state + values." - **Rewrite `otel-a2a-relay` `README.md` `## Deploy`** to the in-tree + OCI + ArgoCD model. - Reconcile closed **#25** (note #45 supersedes). ### Acceptance - No chart templates or Dockerfiles remain under `deploy/services/*/`; only ArgoCD apps + values. - o2r README `## Deploy` and deploy README both describe the in-tree-chart / OCI / ArgoCD model with no contradictions.
coilysiren changed title from o2r packaging: rewrite README Deploy + retire otel-a2a-relay-deploy to o2r packaging: migrate deploy/services chart in-tree; strip coilyco-bridge/deploy to pure GitOps 2026-06-02 23:40:19 +00:00
coilysiren commented 2026-06-17 08:23:45 +00:00
Author
Owner
Copy link

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:45 +00:00
Commenting is not possible because the repository is archived.
No Branch/Tag specified
Branches Tags
main
chore/coilysiren-org-ref-update
dependabot/uv/uv-e1a0e186ab
No results found.
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/otel-a2a-relay#51
No description provided.