0 Releases 6 Tags

RSS Feed

• v0.1.0 b4ccdb09d5

  Compare

  v0.1.0 — a Kubernetes operator for terdut-server

  niklas released this 2026-10-01 13:05:42 +00:00

  First release. Watches TerdutServer, TerdutTeam, TerdutEscalationRule,
  TerdutDeadmanSwitch and TerdutAlertSource CRDs and drives terdut-server's
  own REST API to match: creates and owns every TerdutServer it manages
  (Deployment, Service, database wiring, bootstrap, credentials), mints
  team-scoped credentials for each TerdutTeam, and reconciles each child
  resource's escalation policy, dead man's switch or alert source against
  its team. Full design in DESIGN.md, staged build history in ROADMAP.md.

  Requires terdut-server v0.33.0 for its core operation: the service-account
  API, the v0.33.0 dead man's switch PUT this operator's own reconciler
  depends on for update-in-place. One narrower exception: TerdutTeam's
  crash-recovery path (adopting an already-created team after a reconcile
  that died between POST and status write) also needs
  GET /api/teams?name= (TEAM-LOOKUP.md), which is committed to terdut-server
  main but not yet in a tagged release as of this writing. Not a blocker for
  this release: it installs only the operator and its CRDs, no CR of any
  kind, so no reconcile loop runs until someone applies one.

  Nothing here is irreversible on its own. Installing this chart creates no
  TerdutServer, credential, or webhook key — only the operator Deployment,
  its RBAC, and the five CRDs, all ordinary Kubernetes objects an uninstall
  removes cleanly. The first time anything becomes hard to undo is the first
  TerdutServer or TerdutAlertSource CR someone applies afterward, and that is
  this repo's own documented behavior (DESIGN.md §4.5, §6), not something
  this release changes.

  Downloads

  • Source Code (ZIP)
  • Source Code (TAR.GZ)