T

Niklas Ye 2d8fe0f275 Use a typed escalation fallback instead of fallbackTopic

TerdutTeam spec.escalation.fallback is now {type, address}, mirroring the
server's notification channel model. CRDs regenerated.

Claude-Session: https://claude.ai/code/session_016mBLURvJoMuUEr9cB2RpUN

2026-10-12 21:42:30 +02:00

.gitea/workflows

Build and scan with Go 1.26.9

2026-10-09 15:17:03 +02:00

api/v1alpha1

Use a typed escalation fallback instead of fallbackTopic

2026-10-12 21:42:30 +02:00

charts/terdut-operator

Use a typed escalation fallback instead of fallbackTopic

2026-10-12 21:42:30 +02:00

cmd

Authenticate with a seeded operator key; fold escalation and switches into TerdutTeam

2026-10-09 14:56:22 +02:00

config

Use a typed escalation fallback instead of fallbackTopic

2026-10-12 21:42:30 +02:00

examples

Use a typed escalation fallback instead of fallbackTopic

2026-10-12 21:42:30 +02:00

internal

Use a typed escalation fallback instead of fallbackTopic

2026-10-12 21:42:30 +02:00

.custom-gcl.yml

Scaffold project with Kubebuilder v4

2026-09-30 19:22:09 +02:00

.dockerignore

Stage 1: fix two real bugs the kind e2e pass caught, neither envtest could

2026-10-01 10:15:26 +02:00

.gitignore

Stage 5: installer chart + release infra, kind e2e pass through the chart

2026-10-01 14:47:10 +02:00

.golangci.yml

Scaffold project with Kubebuilder v4

2026-09-30 19:22:09 +02:00

.release.conf

Stage 5: installer chart + release infra, kind e2e pass through the chart

2026-10-01 14:47:10 +02:00

CLAUDE.md

Authenticate with a seeded operator key; fold escalation and switches into TerdutTeam

2026-10-09 14:56:22 +02:00

DESIGN.md

Use a typed escalation fallback instead of fallbackTopic

2026-10-12 21:42:30 +02:00

Dockerfile

Stage 5: installer chart + release infra, kind e2e pass through the chart

2026-10-01 14:47:10 +02:00

go.mod

Update golang.org/x/net to v0.60.0

2026-10-09 22:05:15 +02:00

go.sum

Update golang.org/x/net to v0.60.0

2026-10-09 22:05:15 +02:00

Makefile

Authenticate with a seeded operator key; fold escalation and switches into TerdutTeam

2026-10-09 14:56:22 +02:00

PROJECT

Authenticate with a seeded operator key; fold escalation and switches into TerdutTeam

2026-10-09 14:56:22 +02:00

README.md

Authenticate with a seeded operator key; fold escalation and switches into TerdutTeam

2026-10-09 14:56:22 +02:00

ROADMAP.md

Authenticate with a seeded operator key; fold escalation and switches into TerdutTeam

2026-10-09 14:56:22 +02:00

README.md

Terdut operator

Exposes terdut-server's configuration as Kubernetes objects, so teams can self-service it over gitops. See DESIGN.md for the design (read its revision section first: it is the current shape of credentials and the CRD catalog), and examples/demo for a working install.

CRDs

TerdutServer

A terdut-server install: Deployment, Service, database wiring (a DSN, or a Zalando postgresClusterRef), and an operator key Secret it hands to the server so the operator can authenticate. allowedTeams consents to TerdutTeams in other namespaces.

TerdutTeam

One team on a server, possibly in another namespace (serverRef, gated by that server's allowedTeams). It carries the team's whole configuration:

displayName and OIDC group bindings
escalation — the escalation ladder
deadmanSwitches — dead man's switches, by name (switches not listed are removed)

TerdutAlertSource

An alert-ingest integration on a team (teamRef). The server shows the webhook key once; it is surfaced only through a generated Secret next to the object, never set explicitly.

Demo

examples/demo wires one of each together — two teams, each with an escalation ladder, a dead man's switch and an alert source — plus a script that fires synthetic Alertmanager webhooks at it, so you can watch incidents open, escalate and resolve without a real Alertmanager.