Compare commits

..

60 Commits

Author SHA1 Message Date
AI-Manager 113ebf7c92 Merge pull request 'docs: STATUS.md update for 2026-07-25 triage cycle' (#250) from feature/triage-2026-07-25-cycle into main
Validate Flux manifests / kustomize-build (push) Successful in 18s
Build Docs Site / Aggregate OpenAPI Specs (push) Successful in 2m40s
2026-07-25 20:02:37 +00:00
AI-Agent f3cc3baeed docs: STATUS.md update for 2026-07-25 triage cycle
Validate Flux manifests / kustomize-build (pull_request) Successful in 24s
2026-07-25 20:01:58 +00:00
AI-Manager a51d250efb Merge pull request 'docs: STATUS.md update for 2026-07-16 triage cycle' (#249) from feature/triage-2026-07-16-cycle into main
Validate Flux manifests / kustomize-build (push) Successful in 29s
Build Docs Site / Aggregate OpenAPI Specs (push) Successful in 3m50s
2026-07-16 05:00:49 +00:00
AI-Agent 110c7a813b docs: STATUS.md update for 2026-07-16 triage cycle
Validate Flux manifests / kustomize-build (pull_request) Successful in 24s
All 37 open agent-ready issues re-verified; still gated on operator tasks (#47, #218, #33/#106/#150). kustomize build flux/ = PASS.
2026-07-16 00:02:14 +00:00
AI-Manager ed6d4a6675 Merge pull request 'docs: STATUS.md update for 2026-07-13 triage cycle' (#248) from feature/triage-2026-07-13-cycle into main
Validate Flux manifests / kustomize-build (push) Successful in 15s
Build Docs Site / Aggregate OpenAPI Specs (push) Successful in 2m19s
2026-07-13 20:02:18 +00:00
AI-Agent 317f3fe725 docs: STATUS.md update for 2026-07-13 triage cycle
Validate Flux manifests / kustomize-build (pull_request) Successful in 23s
Refs leeworks-agents/api-company#47 #218
2026-07-13 20:01:56 +00:00
AI-Manager 1843cb63fa Merge pull request 'docs: STATUS.md update for 2026-07-11 triage cycle' (#247) from feature/triage-2026-07-11-cycle into main
Validate Flux manifests / kustomize-build (push) Successful in 15s
Build Docs Site / Aggregate OpenAPI Specs (push) Successful in 2m41s
2026-07-12 00:01:08 +00:00
AI-Agent 35b414b087 docs: STATUS.md update for 2026-07-11 triage cycle
Validate Flux manifests / kustomize-build (pull_request) Successful in 21s
Refs leeworks-agents/api-company#47 #218
2026-07-11 20:02:36 +00:00
AI-Manager 4adb40212a Merge pull request 'docs: STATUS.md update for 2026-07-08 triage cycle' (#246) from feature/triage-2026-07-08-cycle into main
Build Docs Site / Aggregate OpenAPI Specs (push) Failing after 1s
Validate Flux manifests / kustomize-build (push) Failing after 0s
2026-07-08 10:03:10 +00:00
AI-Agent bc9b2b72de docs: STATUS.md update for 2026-07-08 triage cycle
Validate Flux manifests / kustomize-build (pull_request) Successful in 22s
2026-07-08 10:02:49 +00:00
AI-Manager e3368202e2 Merge pull request 'docs: STATUS.md update for 2026-07-04 triage cycle' (#245) from feature/triage-2026-07-04-cycle into main
Validate Flux manifests / kustomize-build (push) Successful in 35s
Build Docs Site / Aggregate OpenAPI Specs (push) Successful in 1m24s
2026-07-04 05:03:18 +00:00
AI-Agent d2f06dc34b docs: STATUS.md update for 2026-07-04 triage cycle
Validate Flux manifests / kustomize-build (pull_request) Successful in 20s
2026-07-04 05:02:50 +00:00
AI-Manager e20e78a9e2 Merge pull request 'docs: update STATUS.md for 2026-06-21 triage cycle' (#244) from feature/triage-2026-06-21-cycle into main
Validate Flux manifests / kustomize-build (push) Successful in 21s
Build Docs Site / Aggregate OpenAPI Specs (push) Successful in 1m22s
2026-06-21 00:03:32 +00:00
AI-Agent 942523411d docs: update STATUS.md for 2026-06-21 triage cycle
Validate Flux manifests / kustomize-build (pull_request) Failing after 28s
2026-06-21 00:03:00 +00:00
0xWheatyz 7d2a8681ab Merge pull request 'fix(ci): repair failing Gitea Actions (validate-flux + build-docs)' (#243) from fix/gitea-actions-failures into main
Validate Flux manifests / kustomize-build (push) Successful in 10s
Build Docs Site / Aggregate OpenAPI Specs (push) Successful in 1m15s
2026-06-20 22:12:00 +00:00
0xWheatyz f841c2216b fix(scripts): unique PAT names + show HTTP error body in token helper
Validate Flux manifests / kustomize-build (pull_request) Successful in 21s
Re-running the helper hit Gitea 400 'token name has been used' because the
token name was only date-stamped. Add time+pid to make names unique, surface
the real HTTP status/body, and continue past a single token failure.
2026-06-20 18:04:16 -04:00
0xWheatyz 98807884b1 fix(ci): authenticate registry push with package-scoped REGISTRY_TOKEN
Validate Flux manifests / kustomize-build (pull_request) Successful in 22s
The auto GITEA_TOKEN has no package-registry scope, so docker login to
gitea.leeworks.dev returned 'unauthorized'. Use a dedicated PAT (REGISTRY_TOKEN,
write:package) with the token-owner username. Helper script now mints both
SIBLING_REPOS_TOKEN and REGISTRY_TOKEN from one password prompt.
2026-06-20 17:53:28 -04:00
0xWheatyz 3cb8f648a1 fix(ci): push docs-site image to gitea.leeworks.dev registry
Validate Flux manifests / kustomize-build (pull_request) Successful in 25s
registry.leeworks.dev serves Traefik's default self-signed cert (TLS verify
fails). Gitea's built-in container registry at gitea.leeworks.dev has a valid
Let's Encrypt cert, so push there instead.
2026-06-20 17:49:43 -04:00
0xWheatyz 3f648cd5a0 fix(ci): install docker CLI in build-docs before registry steps
Validate Flux manifests / kustomize-build (pull_request) Successful in 22s
2026-06-20 17:41:09 -04:00
0xWheatyz a374419400 fix(docs-site): pin @astrojs/sitemap to ~3.2.1 for Astro 4 compat
Validate Flux manifests / kustomize-build (pull_request) Successful in 21s
sitemap 3.7.3 reads opts.routes from astro:build:done, which only exists in
Astro 5; on Astro 4.16 it is undefined and crashes the build with
'Cannot read properties of undefined (reading reduce)'. Pin to the 3.2.x line
and lock it so the docs-site build completes.
2026-06-20 17:35:59 -04:00
0xWheatyz d3f7222db1 build(docs-site): add package-lock.json so 'npm ci' works in CI
Validate Flux manifests / kustomize-build (pull_request) Successful in 21s
2026-06-20 17:31:55 -04:00
0xWheatyz 58e7a8e319 fix(ci): install kustomize via pinned release tarball with retries
Validate Flux manifests / kustomize-build (pull_request) Successful in 22s
2026-06-20 17:29:28 -04:00
0xWheatyz 1949873757 docs(deploy): add Flux/Talos deploy guide + sibling-repos PAT helper script
Validate Flux manifests / kustomize-build (pull_request) Failing after 26s
2026-06-20 17:25:38 -04:00
0xWheatyz ff7c9cfb7e fix(ci): repair failing Gitea Actions 2026-06-20 17:20:26 -04:00
AI-Manager 0cf5780eb8 Merge pull request 'docs: update STATUS.md for 2026-06-15 triage cycle' (#242) from feature/triage-2026-06-15-cycle into main
Build Docs Site / Aggregate OpenAPI Specs (push) Failing after 40s
Validate Flux manifests / kustomize-build (push) Failing after 17s
2026-06-15 10:10:05 +00:00
AI-Agent 3c2c39cb08 docs: update STATUS.md for 2026-06-15 triage cycle
Validate Flux manifests / kustomize-build (pull_request) Failing after 21s
2026-06-15 10:04:46 +00:00
AI-Manager 8c8f751a14 Merge pull request 'docs: update STATUS.md for 2026-06-08 triage cycle #240' (#240) from feature/triage-2026-06-08-cycle-240 into main
Validate Flux manifests / kustomize-build (push) Failing after 9s
Build Docs Site / Aggregate OpenAPI Specs (push) Failing after 37s
2026-06-08 15:07:17 +00:00
AI-Agent 113f09a867 docs: update STATUS.md for 2026-06-08 triage cycle #240
Validate Flux manifests / kustomize-build (pull_request) Failing after 26s
All 28 open agent-ready issues triaged and commented.
All confirmed blocked on operator critical path:
- #47: create 0xWheatyz/api-company (HTTP 404)
- #218: merge 0xWheatyz/Talos PR #14 (Flux activation)
- #33/#106/#150: configure DNS for all 8 subdomains

kustomize build flux/ = PASS
0 open PRs, 0 new issues, 0 issues closed.
2026-06-08 15:06:52 +00:00
AI-Manager 86d45ab9a6 Merge pull request 'docs: fix stale TBD Grafana dashboard reference in metrics-standard.md (#238)' (#239) from feature/fix-metrics-standard-grafana-ref-238 into main
Validate Flux manifests / kustomize-build (push) Failing after 4s
Build Docs Site / Aggregate OpenAPI Specs (push) Failing after 42s
2026-06-08 10:02:04 +00:00
AI-Agent 2c4fc14278 docs: fix stale TBD Grafana dashboard reference in metrics-standard.md
Validate Flux manifests / kustomize-build (pull_request) Failing after 26s
Replace the non-existent docs/grafana-api-dashboard.json reference with
pointers to the actual Flux ConfigMap dashboard locations:
- flux/monitoring/grafana-dashboard-apis.yaml (consolidated 4-API dashboard)
- flux/monitoring/vin-decoder-dashboard.yaml (VIN Decoder-specific dashboard)

Note that dashboards are auto-loaded via grafana_dashboard: "1" label.
Remove the (TBD) annotation — dashboards are already committed.

Closes leeworks-agents/api-company#238
2026-06-08 10:01:33 +00:00
AI-Manager c6165c1e08 Merge pull request 'docs: update STATUS.md for 2026-06-08 triage cycle #237' (#237) from feature/triage-2026-06-08-cycle into main
Build Docs Site / Aggregate OpenAPI Specs (push) Failing after 41s
Validate Flux manifests / kustomize-build (push) Failing after 30s
2026-06-08 05:03:09 +00:00
AI-Agent b88ac14e58 docs: update STATUS.md for 2026-06-08 triage cycle #237
Validate Flux manifests / kustomize-build (pull_request) Failing after 25s
2026-06-08 05:02:23 +00:00
AI-Manager 8fdd2a1edf Merge pull request 'docs: fix STATUS.md Current Blockers — replace closed #174 with open #231' (#236) from feature/fix-status-md-blocker-235 into main
Build Docs Site / Aggregate OpenAPI Specs (push) Failing after 47s
Validate Flux manifests / kustomize-build (push) Failing after 22s
2026-06-07 20:03:12 +00:00
AI-Agent c8271db1ec docs: fix STATUS.md Current Blockers — replace closed #174 with open #231
Validate Flux manifests / kustomize-build (pull_request) Failing after 9s
Issue #174 (VIN Decoder metrics instrumentation) is closed .
Replace stale reference in Current Blockers with open issue #231
(Verify VIN Decoder metrics endpoint and ServiceMonitor scrape config
in live cluster), which correctly tracks the outstanding verification
work. Also bump the 'as of' date to 2026-06-07.

kustomize build flux/ = PASS

Closes leeworks-agents/api-company#235
2026-06-07 20:02:42 +00:00
AI-Manager 7adcc9a524 Merge pull request 'fix: update ROADMAP.md stale issue reference #174#231 (issue #233)' (#234) from feature/fix-roadmap-issue-233 into main
Validate Flux manifests / kustomize-build (push) Failing after 17s
Build Docs Site / Aggregate OpenAPI Specs (push) Failing after 41s
2026-06-07 15:01:55 +00:00
AI-Agent 25045d4ff1 fix: update ROADMAP.md stale issue reference from #174 to #231
Validate Flux manifests / kustomize-build (pull_request) Failing after 20s
Issue #174 (Add VIN Decoder metrics instrumentation) is closed .
The live-cluster verification of VIN Decoder metrics/ServiceMonitor
is now tracked by #231 (open).

Closes leeworks-agents/api-company#233
2026-06-07 15:01:30 +00:00
AI-Manager 7a45bfc369 Merge pull request 'docs: update STATUS.md for 2026-06-07 triage cycle #232' (#232) from feature/triage-2026-06-07-cycle232 into main
Validate Flux manifests / kustomize-build (push) Failing after 21s
Build Docs Site / Aggregate OpenAPI Specs (push) Failing after 43s
2026-06-07 10:03:01 +00:00
AI-Agent 273a41e1fe docs: update STATUS.md for 2026-06-07 triage cycle #232
Validate Flux manifests / kustomize-build (pull_request) Failing after 23s
- 28 agent-ready issues reviewed (27 previously known + new #231)
- Issue #231 triaged: @qa-engineer — VIN Decoder metrics live-cluster
  verification; BLOCKED on #218 (Flux not active)
- kustomize build flux/ PASS
- 0 open PRs
2026-06-07 10:02:32 +00:00
AI-Manager 23dfec20a1 Merge pull request 'fix: add named port 'http' to vin-decoder Service and container for ServiceMonitor scraping' (#230) from feature/fix-vin-decoder-servicemonitor-port into main
Validate Flux manifests / kustomize-build (push) Failing after 21s
Build Docs Site / Aggregate OpenAPI Specs (push) Failing after 37s
2026-06-07 05:06:43 +00:00
AI-Agent cc7172d563 fix: add named port 'http' to vin-decoder Service and container for ServiceMonitor compatibility
Validate Flux manifests / kustomize-build (pull_request) Failing after 20s
The ServiceMonitor at flux/vin-decoder/servicemonitor.yaml references port
by name ('http'), but the Service had anonymous port 80 -> 3000 and the
container had no named port. Prometheus ServiceMonitor port matching requires
the port name to match between the Service and the ServiceMonitor spec.

Adds:
- name: http to the containerPort (port 3000)
- name: http to the Service port (port 80 -> targetPort 3000)

This allows the kube-prometheus-stack ServiceMonitor to correctly scrape
/metrics from vin-decoder pods.

Closes leeworks-agents/api-company#174
2026-06-07 05:06:10 +00:00
AI-Manager 695dac91c4 Merge pull request 'docs: update STATUS.md for 2026-06-07 triage cycle' (#229) from feature/triage-2026-06-07 into main
Build Docs Site / Aggregate OpenAPI Specs (push) Failing after 34s
Validate Flux manifests / kustomize-build (push) Failing after 24s
2026-06-07 00:05:47 +00:00
AI-Agent b2d33a56c4 docs: update STATUS.md for 2026-06-07 triage cycle
Validate Flux manifests / kustomize-build (pull_request) Failing after 25s
- Updated last-updated date to 2026-06-07
- Added Completed This Cycle section for 2026-06-07 triage
- All 27 agent-ready issues triaged and commented
- 0 new issues, 0 closed, 0 PRs, kustomize build PASS
- Critical path unchanged: #47, #218, #33/#106/#150
2026-06-07 00:05:23 +00:00
AI-Agent 8c2cce576e chore: sprint planning cycle #227 — STATUS.md updated (2026-06-06)
Build Docs Site / Aggregate OpenAPI Specs (push) Failing after 59s
Validate Flux manifests / kustomize-build (push) Failing after 38s
Full ROADMAP cross-reference: all 18 unchecked items grounded in open issues, zero gaps.
Staleness check: oldest issue #3/#4 is 19 days old (< 30-day threshold), zero closures.
Label audit: all labels correct from prior cycle, zero changes.
kustomize build flux/ = PASS.
2026-06-06 20:25:07 +00:00
AI-Manager 9c2f228f0c Merge pull request 'docs: update ROADMAP.md Flux wiring entry to reference active tracker #218' (#228) from feature/issue-227-roadmap-flux-ref into main
Validate Flux manifests / kustomize-build (push) Failing after 13s
Build Docs Site / Aggregate OpenAPI Specs (push) Failing after 41s
2026-06-06 20:02:10 +00:00
AI-Agent 1f8014113f docs: update ROADMAP.md Flux wiring ref from closed #2/#187 to active #218
Validate Flux manifests / kustomize-build (pull_request) Failing after 22s
Replace closed issue references (#2, #187) on the Phase 0 Flux
GitRepository entry with the current active tracker #218, which awaits
operator merge of 0xWheatyz/Talos PR #14 to activate Flux GitOps.

Closes leeworks-agents/api-company#227
2026-06-06 20:01:49 +00:00
AI-Manager 9470207b07 Merge pull request 'docs: update STATUS.md for 2026-06-06 triage cycle (#226)' (#226) from feature/issue-226-triage-cycle-2026-06-06 into main
Validate Flux manifests / kustomize-build (push) Failing after 21s
Build Docs Site / Aggregate OpenAPI Specs (push) Failing after 37s
2026-06-06 15:07:01 +00:00
AI-Agent 04a6185824 docs: update STATUS.md for 2026-06-06 triage cycle (#226)
Validate Flux manifests / kustomize-build (pull_request) Failing after 25s
- Triaged all 27 open agent-ready issues; all confirmed blocked on operator
  tasks (create 0xWheatyz/api-company #47, merge Talos PR #14 #218, DNS #33)
- 0 new issues, 0 closures, 0 PRs, kustomize build flux/ = PASS
- Added Completed This Cycle entry for Triage Cycle #226
2026-06-06 15:06:34 +00:00
AI-Manager cde5122702 Merge pull request 'docs: update secrets-checklist.md item #4 for Alertmanager dual consumer (#224)' (#225) from feature/issue-224-secrets-checklist-alertmanager-dual-consumer into main
Build Docs Site / Aggregate OpenAPI Specs (push) Failing after 44s
Validate Flux manifests / kustomize-build (push) Failing after 21s
2026-06-06 10:02:53 +00:00
AI-Agent c7b44b9da6 docs: update secrets-checklist.md item #4 for Alertmanager dual consumer
Validate Flux manifests / kustomize-build (pull_request) Failing after 33s
gatus-slack-webhook (monitoring) is now consumed by two components:
1. Gatus (flux/monitoring/gatus-helmrelease.yaml) - public status-page alerts
2. Alertmanager (flux/monitoring/helmrelease.yaml via alertmanagerSpec.secrets)
   - SLO / firing-alert Slack notifications (enabled by PR #212 / issue #210)

Updates:
- Checklist item #4: mention both Gatus AND Alertmanager Slack SLO alerts
- Secret Details §4: add Consumers row + dual-consumer note explaining
  alertmanagerSpec.secrets mounts this secret and the slack_api_url_file path
- Dependency order: note Alertmanager is also unblocked by item #4

Closes leeworks-agents/api-company#224
2026-06-06 10:02:04 +00:00
AI-Manager 691fe45c13 Merge pull request 'docs: update STATUS.md for 2026-06-06 sprint planning cycle (#221)' (#223) from feature/issue-221-status-update-2026-06-06 into main
Validate Flux manifests / kustomize-build (push) Failing after 7s
Build Docs Site / Aggregate OpenAPI Specs (push) Failing after 54s
2026-06-06 05:03:20 +00:00
AI-Agent 14433e7741 docs: update STATUS.md for 2026-06-06 sprint planning cycle (#221)
Validate Flux manifests / kustomize-build (pull_request) Failing after 22s
- Set Completed This Cycle to Sprint Planning Cycle #221
- Record 0 new issues, 0 closures, 3 label changes (blocked on #106/#150, P1→P2 on #203)
- Update Current Blockers date to 2026-06-06
- kustomize build flux/ = PASS

Closes leeworks-agents/api-company#221
2026-06-06 05:02:53 +00:00
AI-Manager a5aeaf64df Merge pull request 'docs: update STATUS.md blockers — replace closed #187/#90 with open #218' (#220) from feature/issue-219-status-update-blockers into main
Build Docs Site / Aggregate OpenAPI Specs (push) Failing after 46s
Validate Flux manifests / kustomize-build (push) Failing after 16s
2026-06-06 00:04:09 +00:00
AI-Agent 58c6e28ea5 docs: update STATUS.md blockers — replace closed #187/#90 with #218, update Critical Path
Validate Flux manifests / kustomize-build (pull_request) Failing after 51s
Closes leeworks-agents/api-company#219

- Current Blockers item 8: removed P1 #187 and P1 #90 (both closed);
  replaced with P1 #218 (Operator: merge 0xWheatyz/Talos upstream PR #14
  to activate Flux GitOps for api-company)
- Critical Path item 2: updated from #90 reference to #218
- Added Completed This Cycle entry for #219
- kustomize build flux/ = PASS
2026-06-06 00:03:40 +00:00
AI-Manager 321d3e6bf4 Merge pull request 'docs: ROADMAP.md Phase 4 Alertmanager annotation + STATUS.md cycle #215 update' (#216) from feature/issue-214-215-roadmap-status-update into main
Validate Flux manifests / kustomize-build (push) Failing after 21s
Build Docs Site / Aggregate OpenAPI Specs (push) Failing after 3m12s
Validate Flux manifests / kustomize-build (pull_request) Failing after 16s
2026-06-05 15:03:21 +00:00
AI-Agent 14c051fe8f docs: annotate ROADMAP.md Phase 4 Alertmanager + update STATUS.md for cycle #215
Validate Flux manifests / kustomize-build (pull_request) Failing after 25s
- ROADMAP.md: add checked bullet for Alertmanager + Slack receiver (issue #210)
  under Phase 4 Monitoring after VIN Decoder Gatus health check entry.
  Closes leeworks-agents/api-company#214.

- STATUS.md: add Completed This Cycle section for Sprint Planning Cycle #215.
  Documents 1 new issue (#214), 0 closures, 0 label changes, critical path
  unchanged. kustomize build flux/ = PASS.
  Closes leeworks-agents/api-company#215.
2026-06-05 15:02:54 +00:00
AI-Manager 7cb427f4ea Merge pull request 'docs: update STATUS.md for 2026-06-05 sprint planning cycle (#211)' (#213) from feature/issue-211-status-update-2026-06-05 into main
Validate Flux manifests / kustomize-build (push) Failing after 17s
Build Docs Site / Aggregate OpenAPI Specs (push) Failing after 36s
2026-06-05 10:05:27 +00:00
AI-Agent c3ee09b52c docs: update STATUS.md for 2026-06-05 sprint planning cycle (#211)
Validate Flux manifests / kustomize-build (pull_request) Failing after 16s
- Record sprint planning cycle #211 outcomes in Completed This Cycle
- 1 new issue implemented: #210 (Alertmanager + Slack receiver), PR #212 opened
- 0 issues closed (oldest open issue #2, 18 days — under 30-day threshold)
- 0 label changes (all labels confirmed correct)
- ROADMAP cross-reference: 18 unchecked items grounded; 1 gap found + filed (#210)
- Infrastructure section updated with Alertmanager status
- kustomize build flux/ = PASS

Closes leeworks-agents/api-company#211
2026-06-05 10:05:05 +00:00
AI-Manager e3aa6b5fa1 Merge pull request 'feat: enable Alertmanager + Slack receiver in kube-prometheus-stack HelmRelease' (#212) from feature/issue-210-enable-alertmanager into main
Validate Flux manifests / kustomize-build (push) Failing after 22s
Build Docs Site / Aggregate OpenAPI Specs (push) Failing after 46s
2026-06-05 10:04:56 +00:00
AI-Agent 9bc28c2b46 feat: enable Alertmanager with Slack receiver in kube-prometheus-stack HelmRelease
Validate Flux manifests / kustomize-build (pull_request) Failing after 17s
- Set alertmanager.enabled: true (was false)
- Add Slack receiver config pointing to gatus-slack-webhook secret URL
- Add alertmanagerSpec.secrets to mount gatus-slack-webhook into Alertmanager pod
- Route: group by alertname+namespace, 30s wait, 5m interval, 4h repeat
- Channel: #api-alerts with summary title and description text

Closes leeworks-agents/api-company#210
2026-06-05 10:02:29 +00:00
AI-Manager a52bea2552 Merge pull request 'docs: add vin-decoder to pre-launch checklist quick-command snippets' (#209) from feature/fix-checklist-vin-decoder-snippets into main
Validate Flux manifests / kustomize-build (push) Failing after 13s
Build Docs Site / Aggregate OpenAPI Specs (push) Failing after 50s
2026-06-05 05:02:34 +00:00
12 changed files with 8009 additions and 29 deletions
+38 -8
View File
@@ -21,32 +21,38 @@ jobs:
with:
path: api-company
# NOTE: cross-repo checkouts use SIBLING_REPOS_TOKEN, NOT the auto-injected
# GITEA_TOKEN. Gitea's automatic GITEA_TOKEN is scoped to THIS repo only,
# so checking out other repos fails with
# "Determining the default branch → not found". GITEA_TOKEN is also a
# reserved secret name that cannot be overridden, hence a separate secret.
# SIBLING_REPOS_TOKEN must be a PAT with read access to the API repos.
- name: Checkout zip-enrichment
uses: actions/checkout@v4
with:
repository: leeworks-agents/zip-enrichment
token: ${{ secrets.GITEA_TOKEN }}
token: ${{ secrets.SIBLING_REPOS_TOKEN }}
path: zip-enrichment
- name: Checkout holidays
uses: actions/checkout@v4
with:
repository: leeworks-agents/holidays
token: ${{ secrets.GITEA_TOKEN }}
token: ${{ secrets.SIBLING_REPOS_TOKEN }}
path: holidays
- name: Checkout air-quality
uses: actions/checkout@v4
with:
repository: leeworks-agents/air-quality
token: ${{ secrets.GITEA_TOKEN }}
token: ${{ secrets.SIBLING_REPOS_TOKEN }}
path: air-quality
- name: Checkout vin-decoder
uses: actions/checkout@v4
with:
repository: leeworks-agents/vin-decoder
token: ${{ secrets.GITEA_TOKEN }}
token: ${{ secrets.SIBLING_REPOS_TOKEN }}
path: vin-decoder
- name: Copy openapi.yaml specs into docs-site
@@ -72,15 +78,39 @@ jobs:
working-directory: api-company/docs-site
run: npm run build
- name: Log in to container registry
- name: Install Docker CLI
# The job container (node:20) ships no `docker` binary. The runner has a
# dind daemon (dind.enabled in the runner HelmRelease), reachable via
# DOCKER_HOST, so we only need the client. Install the static binary.
env:
DOCKER_CLI_VERSION: "27.3.1"
run: |
echo "${{ secrets.GITEA_TOKEN }}" | docker login registry.leeworks.dev \
-u ${{ gitea.actor }} --password-stdin
set -euxo pipefail
curl -fSL --retry 5 --retry-delay 3 --retry-all-errors \
-o /tmp/docker.tgz \
"https://download.docker.com/linux/static/stable/x86_64/docker-${DOCKER_CLI_VERSION}.tgz"
tar -xzf /tmp/docker.tgz -C /tmp
install -m 0755 /tmp/docker/docker /usr/local/bin/docker
docker version --format '{{.Client.Version}}'
docker info >/dev/null # confirms the dind daemon is reachable
- name: Log in to container registry
# Use Gitea's built-in container registry (gitea.leeworks.dev), which
# has a valid Let's Encrypt cert. The standalone registry.leeworks.dev
# serves Traefik's default self-signed cert and fails TLS verification.
#
# Auth uses REGISTRY_TOKEN, NOT the auto GITEA_TOKEN: the auto token has
# no package-registry scope, and the registry requires the username to
# match the token owner. REGISTRY_TOKEN must be a PAT (owner: 0xWheatyz)
# with write:package + read:package scope.
run: |
echo "${{ secrets.REGISTRY_TOKEN }}" | docker login gitea.leeworks.dev \
-u 0xWheatyz --password-stdin
- name: Build and push docs-site image
working-directory: api-company/docs-site
run: |
IMAGE="registry.leeworks.dev/leeworks-agents/docs-site"
IMAGE="gitea.leeworks.dev/leeworks-agents/docs-site"
SHA="${{ gitea.sha }}"
docker build -t "$IMAGE:$SHA" -t "$IMAGE:latest" .
docker push "$IMAGE:$SHA"
+12 -2
View File
@@ -13,9 +13,19 @@ jobs:
- uses: actions/checkout@v4
- name: Install kustomize
# The act runner runs as root (no `sudo`). Download a pinned release
# tarball directly with retries instead of piping the upstream installer
# script through bash — the installer makes extra GitHub API calls that
# are rate-limited/unreliable on this runner, and `curl -s` hid the
# error (a silent exit 6 = could not resolve host).
env:
KUSTOMIZE_VERSION: "5.4.3"
run: |
curl -sL "https://raw.githubusercontent.com/kubernetes-sigs/kustomize/master/hack/install_kustomize.sh" | bash
sudo mv kustomize /usr/local/bin/
set -euxo pipefail
url="https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv${KUSTOMIZE_VERSION}/kustomize_v${KUSTOMIZE_VERSION}_linux_amd64.tar.gz"
curl -fSL --retry 5 --retry-delay 3 --retry-all-errors -o /tmp/kustomize.tar.gz "$url"
tar -xzf /tmp/kustomize.tar.gz -C /usr/local/bin kustomize
kustomize version
- name: kustomize build flux/
run: kustomize build flux/ > /dev/null
+3 -2
View File
@@ -6,7 +6,7 @@ Cross-repo milestones. Per-API phases live in each API repo's ROADMAP.md.
## Phase 0 — Orientation (one-time)
- [x] Audit cluster: nodes, namespaces, ingress, Flux state → `docs/cluster-audit.md` (issue #36 — closed ✅)
- [ ] Add Flux GitRepository + Kustomization watching `leeworks-agents/api-company` — issue #2 (Talos PR implementation: issue #187)
- [ ] Add Flux GitRepository + Kustomization watching `leeworks-agents/api-company` — issue #218 (fork PR #399 merged to leeworks-agents/Talos; awaiting operator merge of 0xWheatyz/Talos PR #14)
- [ ] Deploy `gitea-act-runner` in cluster via Flux HelmRelease (`flux/gitea-runner/`) — issue #3
- [ ] Stand up `registry.leeworks.dev` (container registry) — required before any API CI works — issue #4
- [ ] Validate ESO HelmRelease deployment and ExternalSecret sync for all 4 API namespaces — issue #178
@@ -29,9 +29,10 @@ Per-API: implement Fastify/FastAPI service matching `openapi.yaml` exactly. Rapi
- [ ] Gatus public status page at `status.leeworks.dev` — issue #8
- [x] Instrument every API with `api_requests_total`, `api_response_duration_seconds`, `api_data_freshness_seconds` (issue #27 — closed ✅)
- [x] Add Prometheus metrics endpoint to holidays service (issue #180 — closed ✅)
- [ ] Verify VIN Decoder metrics endpoint and ServiceMonitor scrape config — issue #174
- [ ] Verify VIN Decoder metrics endpoint and ServiceMonitor scrape config — issue #231
- [x] VIN Decoder metrics instrumentation + Grafana dashboard (issue #129 — closed ✅)
- [x] VIN Decoder Gatus health check (issue #134 — closed ✅)
- [x] Enable Alertmanager in kube-prometheus-stack + configure Slack receiver for SLO alerts (issue #210 — closed ✅)
## Phase 5 — Documentation site
- [x] `docs-site/` Astro + Redoc skeleton (issue #28 — closed ✅)
+164 -7
View File
@@ -1,6 +1,70 @@
# Company Status
_Last updated: 2026-06-05_
_Last updated: 2026-07-25 (triage cycle)_
## Completed This Cycle (2026-07-25 — Triage Cycle)
- **Triage** — All 37 open `agent-ready` issues re-verified against critical-path blockers; no new agent-implementable work surfaced. Every issue remains gated on operator tasks: #47 (populate `0xWheatyz/api-company`), #218 (merge Talos PR #14), #33/#106/#150 (DNS for all 8 subdomains).
- **0 new issues, 0 closures, 0 label changes, 0 open PRs.**
- **`kustomize build flux/` = PASS** (1648 lines, no manifest regressions).
- **Upstream repo `0xWheatyz/api-company` still empty** (Gitea API reports `empty: true`, size 22) — no deployment PRs possible from the agent side; `git fetch upstream` is a no-op.
- **Critical path unchanged:** (1) Operator populates `0xWheatyz/api-company` (#47), (2) Operator merges `0xWheatyz/Talos` PR #14 (#218), (3) Operator configures DNS for all 8 subdomains (#33, #106, #150).
## Completed Previous Cycle (2026-07-16 — Triage Cycle)
- **Triage** — All 37 open `agent-ready` issues re-verified against critical-path blockers; no new agent-implementable work surfaced. Every issue remains gated on operator tasks: #47 (populate `0xWheatyz/api-company`), #218 (merge Talos PR #14), #33/#106/#150 (DNS for all 8 subdomains).
- **0 new issues, 0 closures, 0 label changes, 0 open PRs.**
- **`kustomize build flux/` = PASS** (1648 lines, no manifest regressions).
- **Upstream repo `0xWheatyz/api-company` still empty** (Gitea API reports `empty: true`, size 22) — no deployment PRs possible from the agent side; `git fetch upstream` is a no-op.
- **Critical path unchanged:** (1) Operator populates `0xWheatyz/api-company` (#47), (2) Operator merges `0xWheatyz/Talos` PR #14 (#218), (3) Operator configures DNS for all 8 subdomains (#33, #106, #150).
## Completed Previous Cycle (2026-07-13 — Triage Cycle)
- **Triage** — All 37 open `agent-ready` issues re-verified against critical-path blockers; no new agent-implementable work surfaced. Every issue remains gated on operator tasks: #47 (populate `0xWheatyz/api-company`), #218 (merge Talos PR #14), #33/#106/#150 (DNS for all 8 subdomains).
- **0 new issues, 0 closures, 0 label changes, 0 open PRs.**
- **`kustomize build flux/` = PASS** (1648 lines, no manifest regressions).
- **Upstream repo `0xWheatyz/api-company` still empty** (Gitea API reports `empty: true`, size 22) — no deployment PRs possible from the agent side; `git fetch upstream` is a no-op.
- **Critical path unchanged:** (1) Operator populates `0xWheatyz/api-company` (#47), (2) Operator merges `0xWheatyz/Talos` PR #14 (#218), (3) Operator configures DNS for all 8 subdomains (#33, #106, #150).
## Completed Previous Cycle (2026-07-11 — Triage Cycle)
- **Triage** — All 37 open `agent-ready` issues re-verified against critical-path blockers; no new agent-implementable work surfaced. Every issue remains gated on operator tasks: #47 (populate `0xWheatyz/api-company`), #218 (merge Talos PR #14), #33/#106/#150 (DNS for all 8 subdomains).
- **0 new issues, 0 closures, 0 label changes, 0 open PRs.**
- **`kustomize build flux/` = PASS** (1648 lines, no manifest regressions).
- **Upstream repo `0xWheatyz/api-company` still empty** (Gitea API reports `empty: true`) — no deployment PRs possible from the agent side; `git fetch upstream` is a no-op.
- **Critical path unchanged:** (1) Operator populates `0xWheatyz/api-company` (#47), (2) Operator merges `0xWheatyz/Talos` PR #14 (#218), (3) Operator configures DNS for all 8 subdomains (#33, #106, #150).
## Completed Previous Cycle (2026-07-08 — Triage Cycle)
- **Triage** — All 37 open `agent-ready` issues re-verified against critical-path blockers; no new agent-implementable work surfaced. Every issue remains gated on operator tasks: #47 (create `0xWheatyz/api-company`), #218 (merge Talos PR #14), #33/#106/#150 (DNS for all 8 subdomains).
- **0 new issues, 0 closures, 0 label changes, 0 open PRs.**
- **`kustomize build flux/` = PASS** (1648 lines, no manifest regressions).
- **Upstream repo `0xWheatyz/api-company` still absent** — no deployment PRs possible from the agent side; recent triage comments (2026-07-01/02/04/07) on #241/#179/#66/#47 confirm the block persists.
- **Critical path unchanged:** (1) Operator creates `0xWheatyz/api-company` (#47), (2) Operator merges `0xWheatyz/Talos` PR #14 (#218), (3) Operator configures DNS for all 8 subdomains (#33, #106, #150).
## Completed Previous Cycle (2026-07-04 — Triage Cycle)
- **Triage** — All 37 open `agent-ready` issues reviewed; all confirmed still blocked on the same critical-path operator tasks: #47 (create `0xWheatyz/api-company`), #218 (merge Talos PR #14), #33/#106/#150 (DNS for all 8 subdomains).
- **No agent-implementable work found** — every open issue is either a manual operator task or gated on Flux/cluster activation; kubectl unreachable from agent environment; upstream repo `0xWheatyz/api-company` still absent so no deployment PRs possible.
- **0 new issues, 0 closures, 0 label changes, 0 open PRs.**
- **`kustomize build flux/` = PASS** (1648 lines, no manifest regressions).
- **Critical path unchanged:** (1) Operator creates `0xWheatyz/api-company` (#47), (2) Operator merges `0xWheatyz/Talos` PR #14 (#218), (3) Operator configures DNS for all 8 subdomains (#33, #106, #150).
## Completed Previous Cycle (2026-06-21 — Triage Cycle)
- **Triage** — All 37 open `agent-ready` issues reviewed; all confirmed still blocked on the same critical-path operator tasks: #47 (create `0xWheatyz/api-company`), #218 (merge Talos PR #14), #33/#106/#150 (DNS for all 8 subdomains).
- **No agent-implementable work found** — every open issue is either a manual operator task or gated on Flux/cluster activation; kubectl unreachable from agent environment.
- **0 new issues, 0 closures, 0 label changes, 0 open PRs.**
- **`kustomize build flux/` = PASS** (1648 lines, no manifest regressions).
- **Critical path unchanged:** (1) Operator creates `0xWheatyz/api-company` (#47), (2) Operator merges `0xWheatyz/Talos` PR #14 (#218), (3) Operator configures DNS for all 8 subdomains (#33, #106, #150).
## Completed Previous Cycle (2026-06-15 — Triage Cycle)
- **Triage** — All 38 open `agent-ready` issues reviewed; all confirmed still blocked on the same critical-path operator tasks: #47 (create `0xWheatyz/api-company`), #218 (merge Talos PR #14), #33/#106/#150 (DNS for all 8 subdomains).
- **No agent-implementable work found** — every open issue is either a manual operator task or gated on Flux/cluster activation; kubectl unreachable from agent environment.
- **0 new issues, 0 closures, 0 label changes, 0 open PRs.**
- **`kustomize build flux/` = PASS** (1648 lines, no manifest regressions).
- **Critical path unchanged:** (1) Operator creates `0xWheatyz/api-company` (#47), (2) Operator merges `0xWheatyz/Talos` PR #14 (#218), (3) Operator configures DNS for all 8 subdomains (#33, #106, #150).
## APIs
| API | Spec | Code | Deployed | Listed on RapidAPI | Paying Users | MRR |
@@ -22,8 +86,102 @@ Legend: [x]=done, [~]=in-progress, [ ]=not started
- **API service manifests:** `flux/zip-enrichment/`, `flux/holidays/`, `flux/air-quality/` scaffolded (PR #48, closes #46)
- **Image automation:** `flux/image-automation/` — ImageRepository + ImagePolicy + ImageUpdateAutomation for all three APIs
- **VIN Decoder manifests:** `flux/vin-decoder/` — Flux HelmRelease + Kustomization committed (issue #140)
- **Alertmanager:** `flux/monitoring/helmrelease.yaml` — enabled with Slack receiver config (`gatus-slack-webhook` secret); PR #212 open (issue #210)
## Completed This Cycle (2026-06-05Sprint Planning Cycle #206)
## Completed Previous Cycle (2026-06-08Triage Cycle #240)
- **Triage** — All 28 open `agent-ready` issues reviewed and commented with current status (2026-06-08).
- **All issues confirmed blocked** on the same critical-path operator tasks: #47 (create `0xWheatyz/api-company`), #218 (merge Talos PR #14), #33/#106/#150 (DNS).
- **No agent-implementable work found** — all open issues are either manual operator tasks or gated on Flux/cluster activation; kubectl unreachable from agent environment.
- **28 issues triaged** — status comments posted on all open `agent-ready` issues.
- **0 new issues created** — no gaps found; all ROADMAP items remain grounded in open issues.
- **0 issues closed** — no stale issues; oldest open issue is #3 from 2026-05-18 (21 days < 30-day threshold).
- **0 label changes** — all existing labels correct.
- **0 open PRs** — nothing to review or merge.
- **`kustomize build flux/` = PASS** — no manifest regressions.
- **Critical path unchanged:** (1) Operator creates `0xWheatyz/api-company` (#47), (2) Operator merges `0xWheatyz/Talos` PR #14 (#218), (3) Operator configures DNS for all 8 subdomains (#33, #106, #150).
## Completed Previous Cycle (2026-06-07 — Triage Cycle #232)
- **Triage** — All 28 open `agent-ready` issues reviewed and commented with current status (2026-06-07).
- **All issues confirmed blocked** on the same critical-path operator tasks: #47 (create `0xWheatyz/api-company`), #218 (merge Talos PR #14), #33/#106/#150 (DNS).
- **No agent-implementable work found** — all open issues are either manual operator tasks or gated on Flux/cluster activation; kubectl unreachable from agent environment.
- **1 new issue triaged** — #231 commented with @qa-engineer assessment; BLOCKED on #218.
- **0 new issues created** — no gaps found; all ROADMAP items remain grounded in open issues.
- **0 issues closed** — no stale issues.
- **0 label changes** — all existing labels correct.
- **0 open PRs** — nothing to review or merge.
- **`kustomize build flux/` = PASS** — no manifest regressions.
- **Critical path unchanged:** (1) Operator creates `0xWheatyz/api-company` (#47), (2) Operator merges `0xWheatyz/Talos` PR #14 (#218), (3) Operator configures DNS for all 8 subdomains (#33, #106, #150).
## Completed Previous Cycle (2026-06-06 — Sprint Planning Cycle #227)
- **Sprint Planning** — Full ROADMAP cross-reference + backlog triage completed (2026-06-06).
- **ROADMAP cross-reference:** All 18 unchecked items confirmed grounded in open issues — **zero gaps**.
- Phase 0: #3, #4, #66, #76#83, #126#128, #173, #178, #179, #203, #218 — all tracked.
- Phase 4: #7, #8, #174 — all tracked.
- Phase 5: #30 — tracked.
- Phase 6: #19, #33, #44, #106, #116, #139, #150, #151, #161, #166, #167 — all tracked.
- **Staleness check:** Oldest open issue is #3 / #4 from 2026-05-18 (19 days) — **below 30-day threshold; zero closures**.
- **Label audit:** All priority/complexity labels confirmed correct from cycle #221 audit — **zero changes**.
- **0 new issues created** — no roadmap gaps found.
- **0 issues closed** — no stale issues.
- **0 label changes** — all existing labels correct.
- **`kustomize build flux/` = PASS** — no manifest regressions.
- **Critical path unchanged:** (1) Operator creates `0xWheatyz/api-company` (#47), (2) Operator merges `0xWheatyz/Talos` PR #14 (#218), (3) Operator configures DNS for all 8 subdomains (#33, #106, #150).
## Completed Previous Cycle (2026-06-06 — Triage Cycle #226)
- **Triage** — All 28 open `agent-ready` issues reviewed and commented with current status (2026-06-06).
- **All issues confirmed blocked** on the same critical-path operator tasks: #47 (create `0xWheatyz/api-company`), #218 (merge Talos PR #14), #33/#106/#150 (DNS).
- **No agent-implementable work found** — all open issues are either manual operator tasks or gated on Flux/cluster activation.
- **0 new issues created** — no gaps found; all ROADMAP items are grounded in open issues.
- **0 issues closed** — no issues are stale or resolvable by agent action.
- **0 PRs open** — nothing to review or merge.
- **`kustomize build flux/` = PASS** — no manifest regressions.
- **Current critical path unchanged:** (1) Operator creates `0xWheatyz/api-company` (#47), (2) Operator merges `0xWheatyz/Talos` PR #14 (#218), (3) Operator configures DNS for all 8 subdomains (#33, #106, #150).
## Completed Previous Cycle (2026-06-06 — Sprint Planning Cycle #221)
- **#221** — STATUS.md updated for 2026-06-06 sprint planning cycle (this entry). Last-updated date confirmed 2026-06-06.
- **0 new issues created** — all ROADMAP unchecked items confirmed grounded in open issues (35 open issues, zero gaps).
- **0 issues closed** — oldest open issue is #3 from 2026-05-18 (19 days < 30-day stale threshold).
- **3 label changes:**
- #106 (grafana.leeworks.dev DNS): added `blocked` label (missing despite dependency on #47)
- #150 (vin.leeworks.dev DNS): added `blocked` label (missing despite dependency on #47)
- #203 (ClusterIssuer verification): downgraded P1 → P2 (gated on DNS #33, not a first-order blocker)
- **Critical path unchanged:** Operator must (1) create `0xWheatyz/api-company` (#47), (2) merge upstream Talos PR #14 (#218) to activate Flux, (3) configure DNS (#33, #106, #150).
- **`kustomize build flux/` = PASS** — no manifest regressions.
## Completed Previous Cycle (2026-06-06 — Docs Cycle #219)
- **#219** — STATUS.md Current Blockers updated: removed closed issues #187 and #90; replaced with open issue #218 (Operator: merge 0xWheatyz/Talos upstream PR #14 to activate Flux GitOps for api-company). Critical Path item 2 updated to reference #218. `kustomize build flux/` = PASS.
## Completed Previous Cycle (2026-06-05 — Sprint Planning Cycle #215)
- **#215** — STATUS.md updated for 2026-06-05 sprint planning cycle (this entry). Last-updated date confirmed 2026-06-05.
- **1 new issue created:** #214 (ROADMAP.md Phase 4 Alertmanager annotation — documentation gap filed).
- **0 issues closed** — no stale issues; oldest open issue is #2 from 2026-05-18 (18 days < 30-day threshold).
- **0 label/priority changes** — all existing labels confirmed correct.
- **ROADMAP cross-reference:** all unchecked items confirmed grounded in open issues; 1 new documentation gap found and filed (#214 — Alertmanager / Slack receiver missing from ROADMAP.md Phase 4).
- **Critical path unchanged:** Operator must (1) create `0xWheatyz/api-company` (#47), (2) merge upstream Talos PR #14 (#187) to activate Flux, (3) configure DNS (#33, #106, #150).
- **`kustomize build flux/` = PASS** — no regressions.
- **0 open PRs** — nothing to review or merge.
## Completed Previous Cycle (2026-06-05 — Sprint Planning Cycle #211)
- **#211** — STATUS.md updated for 2026-06-05 sprint planning cycle (this entry). Last-updated date confirmed 2026-06-05.
- **1 new issue implemented:** #210 (Enable Alertmanager + Slack receiver — gap identified by roadmap cross-reference); PR #212 opened to `leeworks-agents/api-company` with `kustomize build flux/` = PASS.
- **0 issues closed** — oldest open issue is #2 from 2026-05-18 (18 days old — under 30-day stale threshold).
- **0 label changes** — all priority/complexity labels confirmed correct.
- **ROADMAP cross-reference:** 18 unchecked items confirmed grounded in open issues; 1 new gap found and filed (#210 — Alertmanager was missing from roadmap coverage).
- **Current Blockers unchanged:** Operator must (1) create `0xWheatyz/api-company` (#47), (2) merge upstream Talos PR #14 (#187) to activate Flux, (3) configure DNS (#33, #106, #150).
- **`kustomize build flux/` = PASS** — no regressions.
- **1 open PR** — PR #212 (Alertmanager enable + Slack receiver): `kustomize build flux/` PASS; pending merge.
## Completed Previous Cycle (2026-06-05 — Sprint Planning Cycle #206)
- **#206** — STATUS.md updated for 2026-06-05 sprint planning cycle (this entry). Last-updated date set to 2026-06-05.
- **Completed outcomes from 2026-06-04 sprint planning cycle recorded:**
@@ -122,7 +280,7 @@ Legend: [x]=done, [~]=in-progress, [ ]=not started
- **PR #160 closed** — had merge conflicts and ROADMAP.md regressions (unchecked completed items). Clean fix applied here.
- **`kustomize build flux/` = PASS** — no regressions.
## Current Blockers (as of 2026-06-04)
## Current Blockers (as of 2026-06-07)
In dependency order — operator tasks unless noted:
@@ -133,11 +291,10 @@ In dependency order — operator tasks unless noted:
5. **P1 #83** — Configure `GITEA_TOKEN` Actions secret in zip-enrichment, holidays, air-quality repos (operator)
6. **P1 #126** — Configure `GITEA_TOKEN` Actions secret in vin-decoder repo (operator — depends on #122 ✅)
7. **P1 #127** — Create `gitea-registry` imagePullSecret in `vin-decoder` namespace (operator)
8. **P1 #187**Merge upstream PR #14 on 0xWheatyz/Talos to activate Flux for api-company (operator) — Fork PR #399 already MERGED to leeworks-agents/Talos; upstream PR #14 is the critical gate; unblocks #2, #3, #4, #66 chain
9. **P1 #90** — Wire Flux GitRepository + Kustomization for api-company in `0xWheatyz/Talos` (superseded by #187; upstream PR #14 pending operator merge)
8. **P1 #218**Operator: merge 0xWheatyz/Talos upstream PR #14 to activate Flux GitOps for api-company — Fork PR #399 already MERGED to leeworks-agents/Talos; upstream PR #14 is the critical gate; unblocks #2, #3, #4, #66 chain (replaces closed #187 and #90)
10. **P2 #80** — Create `gitea-image-automation-token` secret in `flux-system` namespace (operator) — enables Flux image automation
11. **P2 #173** — Create ESO source secrets in `external-secrets` namespace for RapidAPI proxy-secret syncing (operator) — blocks ESO sync
12. **P2 #174** — VIN Decoder metrics instrumentation in `leeworks-agents/vin-decoder` repo (agent task, depends on #18 deploy)
12. **P2 #231** Verify VIN Decoder metrics endpoint and ServiceMonitor scrape config in live cluster (depends on #218 — Flux must be active first)
13. **P2 #178** — Validate ESO HelmRelease deployment and ExternalSecret sync for all 4 API namespaces (depends on #173 + Flux active)
14. **P2 #179** — Execute extended full-stack Flux validation checklist including VIN Decoder (depends on #126, #127, #128)
@@ -181,7 +338,7 @@ In dependency order — operator tasks unless noted:
See **Current Blockers** section above for the full ordered list as of 2026-06-01.
1. **Create `0xWheatyz/api-company` repo** (#47) — **highest priority, unblocks everything**
2. **Add api-company Flux source to Talos** (#90) — needs Talos PR, reference manifests at `flux/api-company-source/`
2. **Merge upstream Talos PR #14 to activate Flux for api-company** (#218) — manifests already committed; operator must merge 0xWheatyz/Talos PR #14
3. **Create `gitea-leeworks-agents-token` secret** in `flux-system` (#76)
4. **Create `gitea-runner-token` secret** in `gitea-runner` (#77)
5. **Enable Gitea packages + DNS for `registry.leeworks.dev`** (#4)
+7567
View File
File diff suppressed because it is too large Load Diff
+2 -2
View File
@@ -8,9 +8,9 @@
"preview": "astro preview"
},
"dependencies": {
"astro": "^4.8.0",
"@astrojs/mdx": "^3.0.0",
"@astrojs/sitemap": "^3.1.0",
"@astrojs/sitemap": "~3.2.1",
"astro": "^4.8.0",
"redoc": "^2.1.5"
},
"devDependencies": {
+120
View File
@@ -0,0 +1,120 @@
# Deploying the APIs (Flux GitOps → Talos)
> Handoff doc. The APIs are **not** deployed by Gitea Actions — they are deployed
> by **Flux** running on the Talos Kubernetes cluster. The Gitea Actions in this
> repo only build the docs-site image, validate Flux manifests, and publish
> OpenAPI specs to RapidAPI.
## How a deploy actually happens
```
API repo (e.g. leeworks-agents/zip-enrichment)
└─ its own CI builds & pushes registry.leeworks.dev/zip-enrichment/server:<tag>
└─ Flux image-automation (flux/image-automation/) rewrites the
{"$imagepolicy": "flux-system:<api>"} marker in flux/<api>/helmrelease.yaml
└─ Flux GitRepository "api-company" (polls main every 5m)
└─ HelmRelease per API (flux/<api>/helmrelease.yaml, bedag/raw chart)
└─ Deployment rolls out in the cluster namespace
```
Each API has its own directory under `flux/`:
| API | Namespace | HelmRelease path | Image |
|---|---|---|---|
| zip-enrichment | `zip-enrichment` | `flux/zip-enrichment/helmrelease.yaml` | `registry.leeworks.dev/zip-enrichment/server` |
| holidays | `holidays` | `flux/holidays/helmrelease.yaml` | `registry.leeworks.dev/holidays/server` |
| air-quality | `air-quality` | `flux/air-quality/helmrelease.yaml` | `registry.leeworks.dev/air-quality/server` |
| vin-decoder | `vin-decoder` | `flux/vin-decoder/helmrelease.yaml` | `registry.leeworks.dev/vin-decoder/server` |
(Confirm each path's exact image with `grep -r imagepolicy flux/`.)
## Prerequisite: the manifests must be live in the cluster's Flux source
`flux/api-company-source/gitrepository.yaml` is **reference only**. The
*authoritative* copy must be committed to **`0xWheatyz/Talos`** at:
```
testing1/first-cluster/cluster/flux/api-company/
```
If that path does not point Flux at this repo's `flux/` directory, Flux never
sees these HelmReleases and nothing deploys. Verify the Talos repo references
this repo's `main` branch and that a Flux `Kustomization` includes the
`api-company` path.
Per-API the cluster also needs (already templated under `flux/<api>/`):
- `namespace.yaml` — the target namespace
- the `gitea-registry` imagePullSecret in that namespace
- `externalsecret.yaml` — pulls API keys (e.g. RapidAPI) via external-secrets
- `servicemonitor.yaml` — Prometheus scraping (optional for deploy)
## One-time local setup (machine with cluster access)
You need tools that are **not** installed on the dev machine yet:
```bash
# Talos kubeconfig — export from the Talos controlplane, e.g.:
# talosctl kubeconfig ~/.kube/talos-leeworks
export KUBECONFIG=~/.kube/talos-leeworks
kubectl cluster-info # must succeed before continuing
# Flux CLI
brew install fluxcd/tap/flux
# Helm (optional, for debugging charts)
brew install helm
flux check # confirm Flux is installed & healthy in-cluster
```
## Deploy / sync all APIs
```bash
export KUBECONFIG=~/.kube/talos-leeworks
# 1. Pull the latest main into the cluster's Git source
flux reconcile source git api-company -n flux-system
# 2. Apply the manifests (name may differ — check: flux get kustomizations -A)
flux reconcile kustomization api-company -n flux-system
# 3. Reconcile each API's HelmRelease
flux reconcile helmrelease zip-enrichment -n zip-enrichment
flux reconcile helmrelease holidays -n holidays
flux reconcile helmrelease air-quality -n air-quality
flux reconcile helmrelease vin-decoder -n vin-decoder
# 4. Verify everything is Ready
flux get helmreleases -A
kubectl get pods -A | grep -E 'zip-enrichment|holidays|air-quality|vin-decoder'
```
## Troubleshooting
```bash
# Why is a release not Ready?
flux get helmrelease <name> -n <ns>
kubectl describe helmrelease <name> -n <ns>
# Is image automation picking up new tags?
flux get image policy -n flux-system
flux get image update -A
# Pod won't start (image pull / secret issues)
kubectl describe pod <pod> -n <ns>
kubectl get events -n <ns> --sort-by=.lastTimestamp | tail -20
```
## Force a fresh deploy of a single API
```bash
flux suspend helmrelease <name> -n <ns>
flux resume helmrelease <name> -n <ns> # triggers a fresh reconcile
# or restart the workload directly:
kubectl rollout restart deployment/<name> -n <ns>
```
## Related docs in this repo
- `docs/operator-runbook.md` — day-2 operations
- `docs/registry.md` — container registry (`registry.leeworks.dev`) setup
- `docs/secrets-checklist.md` — required cluster secrets
- `flux/image-automation/` — automatic image tag bumping
+5 -1
View File
@@ -286,7 +286,11 @@ annotations:
## Grafana Dashboard
A reference dashboard JSON is available at `docs/grafana-api-dashboard.json` (TBD — will be committed once Grafana is deployed per issue #7).
Grafana dashboards are committed as Flux ConfigMaps and are auto-loaded by Grafana via the `grafana_dashboard: "1"` label:
- `flux/monitoring/grafana-dashboard-apis.yaml` — consolidated 4-API dashboard (all APIs)
- `flux/monitoring/vin-decoder-dashboard.yaml` — VIN Decoder-specific dashboard
Dashboards will load automatically once Grafana is deployed (issue #7) and Flux is active (issue #218).
Key panels to include:
1. Request rate by API and status (`rate(api_requests_total[5m])`)
+7 -4
View File
@@ -12,7 +12,7 @@ Follow this list top-to-bottom; each step unblocks the next.
- [ ] 1. `gitea-leeworks-agents-token` (flux-system) — unblocks Flux GitRepository auth
- [ ] 2. `gitea-runner-token` (gitea-runner) — unblocks Gitea Actions runner registration
- [ ] 3. `grafana-admin` (monitoring) — unblocks Grafana login
- [ ] 4. `gatus-slack-webhook` (monitoring) — unblocks Gatus alert notifications
- [ ] 4. `gatus-slack-webhook` (monitoring) — unblocks Gatus alert notifications AND Alertmanager Slack SLO alerts
- [ ] 5. `GITEA_TOKEN` in each API repo's Actions Secrets — unblocks CI image push
- [ ] 6. Gitea packages enabled + DNS record for `registry.leeworks.dev` — unblocks image push to registry
- [ ] 7. Add api-company Flux source + kustomization to 0xWheatyz/Talos — unblocks all GitOps reconciliation
@@ -92,9 +92,12 @@ Grafana will be accessible at `https://grafana.leeworks.dev` (login: `admin` / `
|-----------|-------|
| Name | `gatus-slack-webhook` |
| Namespace | `monitoring` |
| Purpose | Gatus posts downtime alerts to a Slack channel via incoming webhook |
| Purpose | Gatus posts downtime alerts to a Slack channel via incoming webhook. Also mounted by Alertmanager (`alertmanagerSpec.secrets`) to send SLO / firing-alert Slack notifications. |
| Source | Slack → Your workspace → Apps → Incoming Webhooks → Add to Slack → copy webhook URL |
| Unblocks | Issue #8 (Gatus status page at `status.leeworks.dev`) |
| Unblocks | Issue #8 (Gatus status page at `status.leeworks.dev`); Alertmanager Slack receiver (issue #210) |
| Consumers | **Two components** share this secret: (1) **Gatus** (`flux/monitoring/gatus-helmrelease.yaml`) — public status-page alerts; (2) **Alertmanager** (`flux/monitoring/helmrelease.yaml` via `alertmanagerSpec.secrets`) — SLO / firing-alert Slack notifications |
> **Note (dual consumer):** Creating this one secret (`gatus-slack-webhook` in the `monitoring` namespace) unblocks **both** Gatus alert delivery AND Alertmanager's Slack receiver. The Alertmanager configuration references this secret at `global.slack_api_url_file: /etc/alertmanager/secrets/gatus-slack-webhook/url` (enabled in PR #212 / issue #210).
```bash
kubectl create secret generic gatus-slack-webhook \
@@ -266,7 +269,7 @@ kubectl create secret generic rapidapi-proxy-secret \
1 (gitea-leeworks-token) → Flux can pull this repo over HTTPS
2 (gitea-runner-token) → runner online → CI runs
3 (grafana-admin) → Grafana login works
4 (gatus-slack-webhook) → Gatus alerting works
4 (gatus-slack-webhook) → Gatus alerting works + Alertmanager Slack SLO alerts
5 + 6 (GITEA_TOKEN + registry packages) → CI pushes images → API services deploy
8 (gitea-registry) → pods can pull images from registry.leeworks.dev → services start
9 (gitea-image-automation-token) → Flux ImageUpdateAutomation pushes tag-update commits
+19 -1
View File
@@ -85,7 +85,25 @@ spec:
action: replace
target_label: kubernetes_pod_name
alertmanager:
enabled: false # Enable when alert routing is configured
enabled: true
config:
global:
slack_api_url_file: /etc/alertmanager/secrets/gatus-slack-webhook/url
route:
receiver: slack-api-alerts
group_by: [alertname, namespace]
group_wait: 30s
group_interval: 5m
repeat_interval: 4h
receivers:
- name: slack-api-alerts
slack_configs:
- channel: '#api-alerts'
title: '{{ .CommonAnnotations.summary }}'
text: '{{ range .Alerts }}{{ .Annotations.description }}{{ end }}'
alertmanagerSpec:
secrets:
- gatus-slack-webhook
kubeStateMetrics:
enabled: true
nodeExporter:
+4 -2
View File
@@ -37,7 +37,8 @@ spec:
- name: vin-decoder
image: registry.leeworks.dev/vin-decoder/api:latest # {"$imagepolicy": "flux-system:vin-decoder"}
ports:
- containerPort: 3000
- name: http
containerPort: 3000
env:
- name: RAPIDAPI_PROXY_SECRET
valueFrom:
@@ -72,7 +73,8 @@ spec:
selector:
app: vin-decoder
ports:
- port: 80
- name: http
port: 80
targetPort: 3000
- apiVersion: networking.k8s.io/v1
kind: Ingress
+68
View File
@@ -0,0 +1,68 @@
#!/usr/bin/env bash
# Create the Gitea PATs the build-docs workflow needs and store them as action
# secrets on leeworks-agents/api-company:
# - SIBLING_REPOS_TOKEN : read:repository (clone the sibling API repos)
# - REGISTRY_TOKEN : write:package + read:package
# (push the docs-site image to gitea.leeworks.dev)
#
# Why this script exists:
# - The auto-injected GITEA_TOKEN is scoped to THIS repo only (can't read
# sibling repos) and has no package-registry scope (can't push images).
# GITEA_TOKEN is also a reserved secret name that cannot be overridden.
# - `tea` cannot CREATE a PAT (no such command), and Gitea's token-creation
# API requires BASIC AUTH (your password) — a token cannot mint a token.
# - `tea` CAN set the action secrets using its existing login.
#
# So: this prompts for your password ONCE, mints both PATs via the API, and
# pipes each straight into `tea`. Token values are never written to disk.
#
# Usage: bash scripts/setup-sibling-repos-token.sh
set -euo pipefail
GITEA_URL="https://gitea.leeworks.dev"
GITEA_USER="0xWheatyz"
REPO="leeworks-agents/api-company"
# Unique per run (date + seconds + pid) so re-runs never collide with an
# existing PAT name — Gitea returns 400 "token name has been used" otherwise.
STAMP="$(date +%Y%m%d-%H%M%S)-$$"
command -v curl >/dev/null || { echo "curl required"; exit 1; }
command -v tea >/dev/null || { echo "tea required"; exit 1; }
command -v python3 >/dev/null || { echo "python3 required"; exit 1; }
echo "Gitea user: $GITEA_USER ($GITEA_URL)"
read -r -s -p "Gitea password (for $GITEA_USER): " GITEA_PASS
echo
failures=0
# mint_token <token-name> <json-scopes-array> <secret-name>
mint_token() {
local token_name="$1" scopes="$2" secret_name="$3" body code pat
# Capture body + HTTP status separately so 4xx errors show the real message.
body="$(curl -sS -o - -w $'\n%{http_code}' -X POST \
-u "${GITEA_USER}:${GITEA_PASS}" \
-H 'Content-Type: application/json' \
-d "{\"name\":\"${token_name}\",\"scopes\":${scopes}}" \
"${GITEA_URL}/api/v1/users/${GITEA_USER}/tokens")"
code="${body##*$'\n'}"
body="${body%$'\n'*}"
if [ "$code" -lt 200 ] || [ "$code" -ge 300 ]; then
echo "${secret_name}: token API returned HTTP ${code}: ${body}" >&2
echo " (401/403 = wrong password or 2FA; 400 = duplicate name or bad scope)" >&2
failures=$((failures+1)); return 1
fi
pat="$(printf '%s' "$body" | python3 -c 'import sys,json; print(json.load(sys.stdin)["sha1"])' 2>/dev/null || true)"
[ -n "$pat" ] || { echo "${secret_name}: could not parse token from: ${body}" >&2; failures=$((failures+1)); return 1; }
printf '%s' "$pat" | tea actions secrets create "$secret_name" --repo "$REPO" --stdin
echo "${secret_name} set (PAT '${token_name}')"
}
# Don't let one failure abort the rest.
mint_token "sibling-repos-readonly-${STAMP}" '["read:repository"]' "SIBLING_REPOS_TOKEN" || true
mint_token "docs-registry-${STAMP}" '["write:package","read:package"]' "REGISTRY_TOKEN" || true
unset GITEA_PASS
echo "Done (${failures} failure(s)). Verify: tea actions secrets list --repo ${REPO}"
echo "Then re-run build-docs (push to main, or: tea actions workflows dispatch build-docs.yaml)"
[ "$failures" -eq 0 ]