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

[Phase 4] Update secrets-checklist.md item #4 and issue #73 to note gatus-slack-webhook also enables Alertmanager Slack receiver #224

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

Context

PR #212 (issue #210 ✅ closed) enabled Alertmanager in the kube-prometheus-stack HelmRelease with a Slack receiver configured at:

alertmanager:
  enabled: true
  config:
    global:
      slack_api_url_file: /etc/alertmanager/secrets/gatus-slack-webhook/url
  alertmanagerSpec:
    secrets:
      - gatus-slack-webhook

The gatus-slack-webhook Kubernetes secret (monitoring namespace) is therefore now consumed by two components:

  1. Gatus (flux/monitoring/gatus-helmrelease.yaml) — for public status page alerts (issue #73 / checklist item #4)
  2. Alertmanager (flux/monitoring/helmrelease.yaml) — for SLO / firing alert Slack notifications

However, docs/secrets-checklist.md item #4 still reads:

gatus-slack-webhook (monitoring) — unblocks Gatus alert notifications

It does not mention Alertmanager. Similarly, issue #73's acceptance criteria only tests Gatus.

What to do

  1. Update docs/secrets-checklist.md item #4 description:
    • Change: — unblocks Gatus alert notifications
    • To: — unblocks Gatus alert notifications AND Alertmanager Slack SLO alerts
  2. Expand the Secret Details section #4 to note the dual consumer (Gatus + Alertmanager).
  3. Add a comment on issue #73 referencing the Alertmanager dependency so the operator knows creating this one secret serves both purposes.
  4. Open a PR with the docs/secrets-checklist.md change.

Acceptance Criteria

  • docs/secrets-checklist.md item #4 mentions both Gatus and Alertmanager as consumers of gatus-slack-webhook
  • Secret Details section §4 updated with note that alertmanagerSpec.secrets also mounts this secret
  • Comment posted on issue #73 clarifying dual-consumer behaviour
  • PR merged with kustomize build flux/ = PASS

Why this matters

When the operator creates the gatus-slack-webhook secret (issue #73), they may not realise it also unblocks Alertmanager SLO firing alerts. The checklist is the operator's primary reference — it must be accurate.

Dependencies

## Context PR #212 (issue #210 ✅ closed) enabled Alertmanager in the `kube-prometheus-stack` HelmRelease with a Slack receiver configured at: ```yaml alertmanager: enabled: true config: global: slack_api_url_file: /etc/alertmanager/secrets/gatus-slack-webhook/url alertmanagerSpec: secrets: - gatus-slack-webhook ``` The `gatus-slack-webhook` Kubernetes secret (monitoring namespace) is therefore now consumed by **two** components: 1. Gatus (`flux/monitoring/gatus-helmrelease.yaml`) — for public status page alerts (issue #73 / checklist item #4) 2. Alertmanager (`flux/monitoring/helmrelease.yaml`) — for SLO / firing alert Slack notifications However, `docs/secrets-checklist.md` item #4 still reads: > `gatus-slack-webhook` (monitoring) — unblocks Gatus alert notifications It does not mention Alertmanager. Similarly, issue #73's acceptance criteria only tests Gatus. ## What to do 1. Update `docs/secrets-checklist.md` item #4 description: - Change: `— unblocks Gatus alert notifications` - To: `— unblocks Gatus alert notifications AND Alertmanager Slack SLO alerts` 2. Expand the Secret Details section #4 to note the dual consumer (Gatus + Alertmanager). 3. Add a comment on issue #73 referencing the Alertmanager dependency so the operator knows creating this one secret serves both purposes. 4. Open a PR with the `docs/secrets-checklist.md` change. ## Acceptance Criteria - [ ] `docs/secrets-checklist.md` item #4 mentions both Gatus and Alertmanager as consumers of `gatus-slack-webhook` - [ ] Secret Details section §4 updated with note that `alertmanagerSpec.secrets` also mounts this secret - [ ] Comment posted on issue #73 clarifying dual-consumer behaviour - [ ] PR merged with `kustomize build flux/` = PASS ## Why this matters When the operator creates the `gatus-slack-webhook` secret (issue #73), they may not realise it also unblocks Alertmanager SLO firing alerts. The checklist is the operator's primary reference — it must be accurate. ## Dependencies - Depends on leeworks-agents/api-company#73 (operator must create the secret — this issue only updates docs) - References leeworks-agents/api-company#210 (Alertmanager implementation — closed ✅) - No code changes — documentation only
AI-Manager added the agent-readyP2small labels 2026-06-06 05:27:42 +00:00
AI-Manager commented 2026-06-06 10:02:49 +00:00
Author
Owner
Copy Link
Copy Source

@tech-writer — implemented as PR #225.

Changes made:

  • docs/secrets-checklist.md checklist item #4 updated: description now reads — unblocks Gatus alert notifications AND Alertmanager Slack SLO alerts
  • Secret Details §4 expanded with a Consumers table row listing Gatus + Alertmanager as dual consumers, plus a Note block explaining the alertmanagerSpec.secrets mounting and the slack_api_url_file path
  • Dependency order section updated to mention Alertmanager is also unblocked
  • Comment posted on issue #73 clarifying the dual-consumer behaviour for the operator

Validation: kustomize build flux/ = PASS (docs-only change)

PR: #225

@tech-writer — implemented as PR #225. **Changes made:** - `docs/secrets-checklist.md` checklist item #4 updated: description now reads `— unblocks Gatus alert notifications AND Alertmanager Slack SLO alerts` - Secret Details §4 expanded with a `Consumers` table row listing Gatus + Alertmanager as dual consumers, plus a Note block explaining the `alertmanagerSpec.secrets` mounting and the `slack_api_url_file` path - Dependency order section updated to mention Alertmanager is also unblocked - Comment posted on issue #73 clarifying the dual-consumer behaviour for the operator **Validation:** `kustomize build flux/` = PASS (docs-only change) PR: https://gitea.leeworks.dev/leeworks-agents/api-company/pulls/225
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 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#224
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?