Niklas Ye
ca2cd2c645
A self-contained demo kit: a TerdutServer against a throwaway, bare Postgres (bring-your-own DSN -- simplest path to stand up from nothing, ROADMAP.md Stage 1's own note), two TerdutTeams, and each team's own TerdutEscalationRule/TerdutDeadmanSwitch/TerdutAlertSource, so every CRD this operator manages is exercised together rather than in isolation the way config/samples' one-of-each already does. fire-alerts.sh sends terdut-server's own amPayload/amAlert shape (read from internal/api/alertmanager.go in that repo, not guessed from its docs) at whichever TerdutAlertSource's generated webhook Secret it reads the key out of -- high-cpu/disk-full/pod-crash scenarios to open and resolve incidents, and a heartbeat scenario matching each team's dead man's switch matcher, so stopping it demonstrates the switch noticing silence on its own. Verified server-side (kubectl apply --dry-run=server -k examples/demo) against this operator's own dev cluster, which already has these CRDs installed: every object validates. The one warning that cluster's "restricted" PodSecurity raises (postgres:17-alpine's entrypoint needs to start as root before it drops privileges itself) is noted inline in 00-postgres.yaml rather than worked around -- not a real production pattern, and this Postgres exists only to be thrown away with the rest of the demo namespace. README.md walks through: applying, watching status, why a few early CrashLoopBackOff restarts on terdut-demo itself are expected (this operator's Deployment template has no wait-for-postgres init container yet, unlike charts/terdut-server's chart as of v0.33.2), reaching the web UI (port-forward -- spec.networking.hostname is accepted but nothing creates an HTTPRoute for it yet), turning on open signup with the operator's own generated admin token since the bootstrap-created account has no password, firing alerts, and tearing down.
19 lines
738 B
YAML
19 lines
738 B
YAML
# The webhook URL/key fire-alerts.sh sends to, for the Platform team.
|
|
# terdut-server shows the key exactly once, at creation, and never again
|
|
# (DESIGN.md §4.5) -- this object's status.webhookURLSecretRef names the
|
|
# generated Secret holding it (keys "url" and "key"), which is what
|
|
# fire-alerts.sh reads. See README.md before applying this: it's the one
|
|
# object in this directory whose Secret you can't just re-read if you
|
|
# miss it.
|
|
apiVersion: terdut.ryuvia.com/v1alpha1
|
|
kind: TerdutAlertSource
|
|
metadata:
|
|
name: terdutalertsource-platform
|
|
spec:
|
|
teamRef:
|
|
name: terdutteam-platform
|
|
# kind defaults to "alertmanager" -- the only value terdut-server
|
|
# supports today.
|
|
kind: alertmanager
|
|
name: platform-demo-alertmanager
|