Jan Novak
26991fbe13
Completion status previously lived only in my in-session TodoWrite list (ephemeral, doesn't survive the session) or had to be inferred from which steps had an entry in the execution log. Neither is a durable, explicit answer to "what's left." Adds a markdown checklist at the top of each plans-executions file, one line per plan step, checked in the same commit as that step's entry. A new session resuming this plan can read the file alone and know exactly where to pick up. Co-Authored-By: Claude <noreply@anthropic.com>
3.2 KiB
Execution log: proxy-operator
Pairs with docs/plans/2026-08-07-1747-proxy-operator.md.
Status
- Step 0 — Branch and scaffold
- Step 1 — API types (
api/v1alpha1/proxy_types.go) - Step 2 — Provider contract (
internal/provider/) - Step 3 — Mock provider (
internal/provider/mock/) - Step 4 — Reconciler (
internal/controller/) - Step 5 — Health engine (
internal/health/) - Step 6 — Lease store (
internal/lease/) - Step 7 — Discovery API (
internal/discovery/) - Step 8 — GCP provider (
internal/provider/gcp/) - Step 9 — Orphan GC + metrics
- Step 10 — Wiring, config, docs
- Step 11 — Tests
- Verification (vet/test/kind e2e) + commit, push, open MR
Step 0 — Branch and scaffold
Branched off the unborn main:
git checkout -b feat/proxy-operator
Installed kubebuilder v4.15.0 into a scratch GOBIN rather than the default
$(go env GOPATH)/bin, since the module's package layout changed and
go install .../cmd/kubebuilder@v4.15.0 (the path from the plan) 404s — the binary is
now the module root itself:
GOBIN=<scratch>/bin go install sigs.k8s.io/kubebuilder/v4@v4.15.0
Scaffolded in place, with kubebuilder on PATH:
kubebuilder version
# KubeBuilder: v4.15.0, Kubernetes: 1.36.0
kubebuilder init --domain example.com \
--repo gitea.home.hrajfrisbee.cz/kacerr/egress-proxies-operator --plugins go/v4
# WARN: target directory not empty (expected — CLAUDE.md, docs/, .claude/ already existed)
kubebuilder create api --group crawl --version v1alpha1 --kind Proxy \
--resource --controller
create api auto-ran make manifests at the end, which pulled and ran
controller-gen itself:
sigs.k8s.io/controller-tools/cmd/controller-gen@v0.21.0
"$(bin)/controller-gen" object:headerFile="hack/boilerplate.go.txt",year=2026 paths="./..."
Confirmed the CRD group landed correctly (no doubling — --domain example.com --group crawl was used specifically to avoid the crawl.crawl.example.com trap
called out in the plan):
grep -A2 "GroupVersion =" api/v1alpha1/groupversion_info.go
# SchemeGroupVersion = schema.GroupVersion{Group: "crawl.example.com", Version: "v1alpha1"}
Dropped the scaffolded GitHub Actions workflows (remote is Gitea, not GitHub):
git rm -r --cached .github 2>/dev/null; rm -rf .github
Ran the full manifest/codegen pass once more to confirm the toolchain is reproducible end to end:
make manifests generate
# controller-gen rbac:roleName=manager-role crd webhook paths="./..." output:crd:artifacts:config=config/crd/bases
# controller-gen object:headerFile="hack/boilerplate.go.txt",year=2026 paths="./..."
then go build ./... and go vet ./..., both clean with no output.
Worth noting: CONTROLLER_TOOLS_VERSION in the generated Makefile came out at
v0.21.0 by default in this kubebuilder release, so the Makefile edit the plan
anticipated wasn't needed. Pre-existing CLAUDE.md/CHANGELOG.md content survived
untouched; kubebuilder added its own README.md, AGENTS.md, .golangci.yml,
.devcontainer/, Dockerfile on top of them — those get edited or left as-is in
later steps. Committed as 076bc66.