docs: record what the CRD design got wrong and how it shipped #54

Merged
ivuorinen merged 1 commit from docs/crd-spec-outcome into main 2026-09-26 13:38:04 +00:00
Owner

Records the outcome on the CRD automation design, the way
2026-09-20-tailscale-design.md does — 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:

  • The hook-only shape does not work. ArgoCD excludes hooks from its
    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 crds returns nothing for External Secrets, which keeps its
    CRDs behind installCRDs rather than in the chart's crds/ directory.

Also notes that the plan's Renovate grouping task was dropped: promtool is
disabled 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.

Records the outcome on the CRD automation design, the way `2026-09-20-tailscale-design.md` does — 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: - **The hook-only shape does not work.** ArgoCD excludes hooks from its 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 crds` returns nothing for External Secrets**, which keeps its CRDs behind `installCRDs` rather than in the chart's `crds/` directory. Also notes that the plan's Renovate grouping task was dropped: `promtool` is disabled 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.
docs: record what the CRD design got wrong and how it shipped
All checks were successful
validate / render (pull_request) Successful in 48s
validate / hooks (pull_request) Successful in 1m30s
66fc7445da
ivuorinen deleted branch docs/crd-spec-outcome 2026-09-26 13:38:05 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ivuorinen/turingpi-cluster!54
No description provided.