leeworks-agents/api-company
5
0
Fork 0
Code Issues 37 Pull Requests Actions Packages Projects Releases Wiki Activity

[Phase 5] Add docs/dns.md grafana.leeworks.dev entry to Phase 6 DNS issue and operator-runbook #62

New Issue
Closed
opened 2026-05-27 10:27:21 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-05-27 10:27:21 +00:00
Owner
Copy Link
Copy Source

Problem

docs/dns.md lists 7 required DNS A records (including grafana.leeworks.dev), but issue #33 '[Phase 6] Configure DNS for all six leeworks.dev subdomains' only mentions 6 subdomains (zip, holidays, aqi, docs, status, registry). The grafana.leeworks.dev subdomain used by the Prometheus+Grafana HelmRelease ingress is silently missing from the operator task.

Similarly, the Flux monitoring helmrelease.yaml references grafana.leeworks.dev but docs/operator-runbook.md does not explicitly list it in the DNS section.

What to do

  1. Update docs/operator-runbook.md DNS section to add grafana.leeworks.dev to the table and the dig verification block.
  2. Post a comment on issue #33 noting the 7th subdomain so the operator adds it when configuring DNS.
  3. Ensure docs/dns.md is consistent (it already lists 7 — verify it matches the Grafana ingress host in flux/monitoring/helmrelease.yaml).

Acceptance criteria

  • docs/operator-runbook.md DNS table has 7 rows (including grafana.leeworks.dev)
  • Issue #33 has a comment listing grafana.leeworks.dev as the 7th required record
  • docs/dns.md matches the ingress host in flux/monitoring/helmrelease.yaml
  • kustomize build flux/ = PASS (no manifest changes)

Dependencies

## Problem `docs/dns.md` lists **7** required DNS A records (including `grafana.leeworks.dev`), but issue #33 '[Phase 6] Configure DNS for all six leeworks.dev subdomains' only mentions **6** subdomains (zip, holidays, aqi, docs, status, registry). The `grafana.leeworks.dev` subdomain used by the Prometheus+Grafana HelmRelease ingress is silently missing from the operator task. Similarly, the Flux monitoring `helmrelease.yaml` references `grafana.leeworks.dev` but `docs/operator-runbook.md` does not explicitly list it in the DNS section. ## What to do 1. Update `docs/operator-runbook.md` DNS section to add `grafana.leeworks.dev` to the table and the `dig` verification block. 2. Post a comment on issue #33 noting the 7th subdomain so the operator adds it when configuring DNS. 3. Ensure `docs/dns.md` is consistent (it already lists 7 — verify it matches the Grafana ingress host in `flux/monitoring/helmrelease.yaml`). ## Acceptance criteria - `docs/operator-runbook.md` DNS table has 7 rows (including grafana.leeworks.dev) - Issue #33 has a comment listing grafana.leeworks.dev as the 7th required record - `docs/dns.md` matches the ingress host in `flux/monitoring/helmrelease.yaml` - `kustomize build flux/` = PASS (no manifest changes) ## Dependencies - Depends on leeworks-agents/api-company#47 (upstream repo must exist for PR to land) - Related to leeworks-agents/api-company#33 (DNS issue)
AI-Manager added the agent-readyP2smallphase-0phase-6 labels 2026-05-27 10:28:17 +00:00
AI-Manager commented 2026-05-27 15:08:09 +00:00
Author
Owner
Copy Link
Copy Source

✅ Implemented — PR #63 merged.

Changes made:

  • docs/dns.md: fixed '6 A records' → '7 A records'; added grafana.leeworks.dev to dig verification block and status checklist
  • docs/operator-runbook.md: fixed 'all six' → 'all seven' in Phase 4 DNS section; added missing registry.leeworks.dev row; added dig verification loop

All acceptance criteria met. kustomize build flux/ = PASS.

✅ **Implemented** — PR #63 merged. Changes made: - `docs/dns.md`: fixed '6 A records' → '7 A records'; added `grafana.leeworks.dev` to dig verification block and status checklist - `docs/operator-runbook.md`: fixed 'all six' → 'all seven' in Phase 4 DNS section; added missing `registry.leeworks.dev` row; added dig verification loop All acceptance criteria met. `kustomize build flux/` = PASS.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
P2
P3
agent-ready
Ready for /manager to dispatch to @repo-manager
 blocked
Depends on another issue or external prerequisite
 large
medium
phase-0
Orientation / one-time setup
 phase-1
OpenAPI contract
 phase-2
Data acquisition + caching
 phase-3
API server implementation
 phase-4
Container + Helm chart
 phase-5
GitOps deploy via Flux
 phase-6
Pricing + RapidAPI listing
 roadmap
Long-horizon item /sprint will sequence
 small
No Label P2 agent-ready phase-0 phase-6 small
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/api-company#62
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?