docs: record what the CRD design got wrong and how it shipped #54
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/crd-spec-outcome"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Records the outcome on the CRD automation design, the way
2026-09-20-tailscale-design.mddoes — including what the design got wrong,since that is the part worth having written down.
Two design-level errors, both found only by running the thing:
desired-vs-live comparison, so an all-hook Application never syncs. #49 went
Synced/Healthy in two minutes and did nothing at all. The same exclusion means
a version inside a hook never re-triggers a sync, so "add any normal resource"
would have fixed the first sync and left every later bump silently doing
nothing.
helm show crdsreturns nothing for External Secrets, which keeps itsCRDs behind
installCRDsrather than in the chart'scrds/directory.Also notes that the plan's Renovate grouping task was dropped:
promtoolisdisabled deliberately because the Prometheus version is internal to the chart,
so a group would have produced mismatched PRs rather than fewer.
Docs only — no manifests, no scripts, no behaviour change.