# terdut-operator

Kubebuilder/controller-runtime operator for terdut-server. See `DESIGN.md` for the
settled design (CRD catalog, reconciliation semantics, bootstrap/auth, RBAC) and
`ROADMAP.md` for the staged build plan this repo is following. `README.md` stays the
short pitch.

## Checks

`make fmt lint test` is the CI gate (`.gitea/workflows/ci.yaml` calls these targets
rather than restating them, same convention as terdut-server). `test` chains through
the Kubebuilder-scaffolded `manifests`/`generate` (`controller-gen`) and `setup-envtest`
targets automatically — everything needed lands in `bin/` (gitignored) on first run, no
separate tool install required beyond Go itself and network access to
`proxy.golang.org`/`storage.googleapis.com`.

`make test-e2e` stands up a real `kind` cluster (`kind`/`docker` must be installed) and
is not part of the CI gate yet — it has no service-image to test against until later
ROADMAP stages produce one.

## Release

Not wired yet. `.release.conf` and the release-vars Makefile target land in ROADMAP.md's
Stage 6, once there's an actual Helm chart to release — see that file before assuming
the `release` skill's terdut-server/terdut-tui conventions already apply here.