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.
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.
Closesleeworks-agents/api-company#227
- 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
Closesleeworks-agents/api-company#221
- 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
Closesleeworks-agents/api-company#210
Fix three omissions in the Quick Commands Reference section:
1. Pod-health loop: add vin-decoder to namespace list
2. DNS check loop: add vin subdomain (8th subdomain, not 7)
3. Health smoke-test loop: add vin.leeworks.dev/v1/health
Closesleeworks-agents/api-company#208
- **Alertmanager:** `flux/monitoring/helmrelease.yaml` — enabled with Slack receiver config (`gatus-slack-webhook` secret); PR #212 open (issue #210)
## Completed This Cycle (2026-06-05 — Sprint Planning Cycle #206)
## Completed This Cycle (2026-06-07 — Triage Cycle)
- **Triage** — All 27 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.
- **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).
- **#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.
- **#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.
- [ ] 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. |
| 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).
text:'{{ range .Alerts }}{{ .Annotations.description }}{{ end }}'
alertmanagerSpec:
secrets:
- gatus-slack-webhook
kubeStateMetrics:
enabled:true
nodeExporter:
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.