Niklas Ye
b4ccdb09d5
Release / test (push) Successful in 2m48s
CI / chart (push) Successful in 1s
CI / security (push) Successful in 1m3s
CI / test (push) Successful in 2m5s
Release / chart (push) Successful in 4s
Release / image (push) Successful in 7m6s
Release / scan-image (push) Failing after 33s
Chart (charts/terdut-operator) generated via kubebuilder's own helm/v2-alpha plugin from config/'s kustomize output -- CRDs + manager Deployment/RBAC come from the same markers every other stage already generates, one source of truth. Hand-added on top: the optional terdutServer values block (DESIGN.md §10's "helm install and get a server" path, off by default) and the release-skill plumbing -- .release.conf, release-vars/helm-lint/push/ helm-package/helm-push/release Makefile targets, .gitea/workflows/release.yaml (test -> image/chart -> scan-image) -- mirroring terdut-server's own shape (registry/namespace convention, multi-arch buildx push, trivy/govulncheck/ gitleaks scans). ci.yaml gains security and chart jobs to match. Two real issues caught while wiring this, fixed before either shipped: - Dockerfile's builder stage didn't pin --platform=$BUILDPLATFORM, which would have made a multi-arch release build fail outright on this org's runners (no binfmt registration) -- same fix terdut-server's own Dockerfile already needed for the same reason. - govulncheck found one real, reachable finding: google.golang.org/grpc v1.82.1 (transitive via controller-runtime's otel exporter), fixed by bumping to v1.83.1. Full golden-path kind e2e pass, this time through `helm install` rather than raw kustomize: TerdutServer (real terdut-server v0.33.0 image) -> TerdutTeam -> one of each child kind, each confirmed Ready and then independently confirmed against terdut-server's own API from inside the cluster (not just the operator's own status). Deleted every CR in reverse order and confirmed server-side cleanup the same independent way for all three child kinds, the team, and the server. No new bugs found -- Stage 1's own kind pass already caught what a real cluster catches that envtest can't. Also dropped the kubebuilder helm plugin's default .github/workflows/ scaffold, same as Stage 0 already did for the main scaffold: this org runs on Gitea, not GitHub. Not done here, deliberately: an actual tagged release. release-preflight found no terdut-operator/ entry under Ryuvia/charts yet to bump -- that one-time wrapper bootstrap is a decision about deploying this operator for real, not a side effect of finishing this stage. make fmt lint test helm-lint build all clean.
22 lines
952 B
Plaintext
22 lines
952 B
Plaintext
# Read by the `release` skill (~/.claude/skills/release).
|
|
#
|
|
# Only what the Makefile cannot already say. IMAGE, HELM_CHART and HELM_REPO come from
|
|
# `make release-vars`, so they have one definition and cannot drift from what is built.
|
|
#
|
|
# Defaults, set here only where this repo differs:
|
|
# CHARTS_REPO=$HOME/git/charts CHARTS_DIR=<image basename>
|
|
# GITEA_LOGIN=Ryuvia APPVERSION_PREFIX=
|
|
# PROSE_LANG=en
|
|
|
|
# Same as the image basename, so this is only stated to be read rather than derived.
|
|
CHARTS_DIR=terdut-operator
|
|
|
|
# This repo writes appVersion: "v0.1.0" (see charts/terdut-operator/Chart.yaml),
|
|
# matching terdut-server's own v-prefixed style -- nothing reads the field, but people
|
|
# do, and it should say the same thing the release tag does.
|
|
APPVERSION_PREFIX=v
|
|
|
|
# English, for the same reason as terdut-server: this is an on-call tool's operator,
|
|
# and nothing about its labels, API or docs is coupled to Swedish.
|
|
PROSE_LANG=en
|