Niklas Ye
0e89816ad4
CI / test (push) Successful in 7m59s
Clean result, isolated from lint's own unrelated github.com flakiness: post-MTU-fix (Ryuvia/charts#272), `make test` alone hits the exact same "TLS handshake timeout" fetching envtest-v1.37.0-linux-amd64.tar.gz as before the fix. Byte-for-byte identical error. The dind sidecar's MTU mismatch was real (measured 1450 vs 1500 per the other session's report) but it was not (solely) the cause of this specific failure. Separately and incidentally: golangci-lint's own custom-gcl build also does a plain `git clone https://github.com/...` and that is now failing too (2/2, ~2.5min hang then generic exit 128) where it briefly succeeded in an earlier pre-fix run -- noted in the comment but not chased further here; worth someone's attention if it keeps recurring, since it'll block `lint` regardless of the envtest question.
Terdut operator
Aims to expose most config as CRD's, so end users can self-service over gitops.
See DESIGN.md for the full design: CRD catalog and specs,
reconciliation semantics, bootstrap/auth, Postgres integration, RBAC, and the
relationship to charts/terdut-server. This README stays a short pitch; the
open questions it used to carry are now resolved decisions there (§2).
CRD's
terdutServers
Creates a server — Deployment, Service, database wiring, bootstrap, operator
credentials, and allowedTeams consent for cross-namespace teams. See
DESIGN.md §4.1, §4.6.
terdutTeams
- team name
- oidc groups
serverRef— explicit reference to itsTerdutServer, may be in a different namespace (one team owns the server, others self-service a team against it), gated by thatTerdutServer's ownallowedTeamsfield (DESIGN.md §2, §4.1, §4.2, §4.6)
terdutEscalationrules
- rule
teamRef— explicit reference to itsTerdutTeam(DESIGN.md §2, §4.3)
terdutDeadmansswitches
- rule
teamRef(DESIGN.md §4.4)
terdutAlertSources
teamRef(DESIGN.md §4.5)- URL/key are generated by the server at creation and surfaced only via a generated Secret, never set explicitly